-
Notifications
You must be signed in to change notification settings - Fork 158
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
update: cert-manager #265
update: cert-manager #265
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of quick questions on this one.
Let me know if you think it should be updated.
apiVersion: kustomize.config.k8s.io/v1beta1 | ||
kind: Kustomization | ||
|
||
namespace: cert-manager-operator |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally I prefer to keep the namespace in the kustomize, especially when you are dealing with multiple objects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think most operators in the catalog use this pattern. Can we do this as a separate PR?
@@ -1,9 +1,8 @@ | |||
apiVersion: operators.coreos.com/v1 | |||
kind: OperatorGroup | |||
metadata: | |||
name: cert-manager-operator | |||
name: openshift-cert-manager-operator-group |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it is a requirement, but I think normally the operator groups name is the same as the namespace. I would prefer to keep it the same as whatever the GUI creates when installing through the UI so if someone installs via the UI and then later adds the catalog item into gitops, it doesn't cause a second operator group to be created.
Can you confirm what the correct operatorgroup name should be?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with aligning the name of the operator group with the packagemanifest name, that might also be the namespace name... Either way we can remove the -group
because it's redundant. This should be removed globally and in the script used to generate operators. I can do that in another PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this was an exception with naming of things. We can dig into it more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM?
@@ -1,9 +1,8 @@ | |||
apiVersion: operators.coreos.com/v1 | |||
kind: OperatorGroup | |||
metadata: | |||
name: cert-manager-operator | |||
name: openshift-cert-manager-operator-group |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this was an exception with naming of things. We can dig into it more.
@strangiato We good to merge this? |
@strangiato ... bump :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
No description provided.