-
Notifications
You must be signed in to change notification settings - Fork 207
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
MGMT-18131: Make application work on non-OCP kubernetes (#6446)
* Add API to AgentServiceConfig for ingress hostnames These will be used to create ingress resources when not running on an OCP cluster. https://issues.redhat.com/browse/MGMT-18131 * Skip webhooks and https to get the services deployed There is no way to deploy our webhooks without tls config and deciding on a way to manage certificates is out of the scope of this patch. https://issues.redhat.com/browse/MGMT-18131 * Deploy ingress instead of routes when not running in OCP This will allow traffic based on a hostname and on a standard port rather than using hostport type services. https://issues.redhat.com/browse/MGMT-18131 * Add ingress class name API If a user hasn't marked a particular ingress class as the default they will need to specify an ingress class. https://issues.redhat.com/browse/MGMT-18131 * Document deploying the operator on a kind cluster for dev * Create a separate struct for ingress config * Make ingress hostnames required and ingress itself properly optional This also adds a validation to ensure that Ingress is provided if the operator is running on a non-OpenShift kubernetes platform
- Loading branch information
Showing
18 changed files
with
907 additions
and
123 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.