-
Notifications
You must be signed in to change notification settings - Fork 33
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
Improved Kuadrant installation via Olm and kustomize #1075
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1075 +/- ##
==========================================
+ Coverage 76.15% 83.73% +7.57%
==========================================
Files 111 81 -30
Lines 8986 6712 -2274
==========================================
- Hits 6843 5620 -1223
+ Misses 1852 872 -980
+ Partials 291 220 -71
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Signed-off-by: craig <[email protected]> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED more detailed installation guide and examples rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
77c9151
to
93292e8
Compare
Signed-off-by: craig <[email protected]> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
Signed-off-by: craig <[email protected]> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
Signed-off-by: craig <[email protected]> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
Signed-off-by: craig <[email protected]> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
Re-Apply the configuration to setup the new secret and configuration: | ||
|
||
```bash | ||
kubectl apply -k $KUADRANT_DIR/configure/ |
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.
This fails with an error
kubectl apply -k $KUADRANT_DIR/configure/
error: no resource matches strategic merge patch "Limitador.v1alpha1.limitador.kuadrant.io/limitador.kuadrant-system": no matches for Id Limitador.v1alpha1.limitador.kuadrant.io/limitador.kuadrant-system; failed to find unique target for patch Limitador.v1alpha1.limitador.kuadrant.io/limitador.kuadrant-system
Presumably becuase the Limitador CR is not part of the resources included in the kustomization, but you want to patch it.
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.
Probably related to changes below https://github.com/Kuadrant/kuadrant-operator/pull/1075/files#diff-36411ee7f394bd28aaa769d3b33d193cde1e03f8f7bb3fd569b2efb1b4a509f0R4
would need to land that on the v1.0.1 branch
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.
Yes I want to cherry pick these changes to the v1.0.1 branch. In the validation steps I mentioned you would have to use the ref=olm-installation for the resources .
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 got to end of the doc, including the redis, TopologyConstraints, PodDisruptionBudget and Resource Limits pieces.
Comments and suggestions above.
Co-authored-by: David Martin <[email protected]>
Co-authored-by: David Martin <[email protected]>
Co-authored-by: David Martin <[email protected]>
Co-authored-by: David Martin <[email protected]>
Signed-off-by: craig <[email protected]> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
/cherry-pick release-v1.0.1 |
What This updates the install with more details and hopefully clearer instructions.
The guide is focused around OLM and kustomize. Having this doesn't mean we can't also have a helm or kustomize without an OLM requirement
Verfication
Follow the guide without needing to clone the repo, You should be able to use a basic kind cluster.
Note
You will have to set the version in the configure/kustomization.yaml resource paths from
v1.0.1
toolm-installation
as some of the changes on this branch are not yet on the v1.0.1 branchStill to do