Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Openshift (k8s), introduce a dry-run or another provisioning target to just generate resources #80

Closed
jfdenise opened this issue Jun 20, 2024 · 0 comments · Fixed by #81

Comments

@jfdenise
Copy link
Contributor

The current openshift targets requires to be connected to an OpenShift cluster. The image build is operated by OpenShift S2I binary buid.
There is a need to only produce Docker files and k8s resources without provisioning the server not connecting to the cluster.
Such dry-run mode should allow:

  • To produce an image based on the generated Docker Files with a provisioned server.
  • To produce k8s resources that could then be added to the cluster.
jfdenise added a commit to jfdenise/wildfly-glow that referenced this issue Jun 27, 2024
… stability, use channels when computing server hash for server image
jfdenise added a commit to jfdenise/wildfly-glow that referenced this issue Jun 28, 2024
… stability, use channels when computing server hash for server image
jfdenise added a commit that referenced this issue Jun 28, 2024
Fix for Issue #80, OpenShift dry-run mode. Fix channels handling, cleanup default stability
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant