-
Notifications
You must be signed in to change notification settings - Fork 30
Changes for RH Certification #5
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.
@Rulox please see my comments.
Additionally,
Generated a few versions (current 0.0.3) as examples. Next release should be done in GitHub as well as the first release. It is important we keep all versions (check community operators) (maybe bundle/ folder is too much? bundle is the actual version but all the fields are in the other folders, let me know and I'll remove this and add it to gitignore)
I feel it is too much, since we can generate the bundle. I wonder if it is a release artifact and should be a part of a GH release 🤔
Also, if we don't have the bundle directory there, we will not need to make sure that bundle directory is updated. For example, If I run make generate-bundle
, the files in bundle are changed. Is it expected?
modified: bundle/k8s.nginx.org_nginxingresscontrollers_crd.yaml
modified: bundle/nginx-ingress-operator.v0.0.2.clusterserviceversion.yaml
modified: bundle/nginx-ingress-operator.v0.0.3.clusterserviceversion.yaml
...
--- a/bundle/nginx-ingress-operator.v0.0.2.clusterserviceversion.yaml
+++ b/bundle/nginx-ingress-operator.v0.0.2.clusterserviceversion.yaml
@@ -323,7 +323,7 @@ spec:
type: SingleNamespace
- supported: false
type: MultiNamespace
- - supported: true
+ - supported: false
type: AllNamespaces
Agreed, I'll remove bundle from repository. The bundle folder is just an intermediate step to build the required PS: Yeah the manfiests are not updated because I was waiting on a bug resolution by RH in order to update here. Will update everything with feedback provided, thanks. |
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. Just one typo
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.
👍
Proposed changes
This PR includes everything that is required to get the RH Certification of the operator, including helpers to make new releases faster. Please keep in mind these changes were done only for certification, not because they make 100% sense.
Deployment
field which will be set to true if there were no errors deploying the KIC. For now it's just set to true after deploying everything, but in the future this could be more intelligent maybe.bundle/
folder is too much? bundle is the actual version but all the fields are in the other folders, let me know and I'll remove this and add it to gitignore)Additional BugFixes and docs changes:
imagePullPolicy
triggers the operator to change the Deployment/Daemonset-trimpath
build parameter instead of go builds. This was the only way to prevent $GOPATH to be in the final binary. Trimpath as build argument is working since Go 1.13. (cc @dboenig this change might affect pipelines, please have a look at the Makefile thanks)I will squash commits before merge.