Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #74
This PR is to install cert-manager and RMQ operators (RMQ cluster operator ,RMQ topology operator) on our K8 cluster.
This PR contains:
Cluster-operator is a straight forward installation where ArgoCD will read the cluster-operator.yml and deploy , thus creating CRs /CRDs, essentially "partly" automating the installation. Partly because we'll manually have to download the latest release (can be done by Github actions as well )
There are 2 ways to install Topology operator
The current PR installs this operator with cert-manager. We can go with generated certificates but as per the documentation it would require us to make changes to the messaging-topology-operator.yaml
"The Messaging Topology Operator has multiple admission webhooks. Their endpoints are TLS-enabled and require a webhook certificate that must be used in multiple places in the downloaded release manifest."
"Finally, add webhook's CA certificate to the release manifest, messaging-topology-operator.yaml. There are multiple admission webhooks, one for each CRD type.
Look for keyword
clientConfigin the manifest, and paste the webhook CA certificate under clientConfig.caBundle. Because there are several webhooks, perform this action in several places."This would be an extra overhead, and chances of missing a CRD is high. cert-manager itself is quite secure and is used widely.