-
Notifications
You must be signed in to change notification settings - Fork 345
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
Use es-operator from 4.1 branch #537
Use es-operator from 4.1 branch #537
Conversation
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
@kubectl apply -f https://raw.githubusercontent.com/openshift/elasticsearch-operator/release-${ES_OPERATOR_VERSION}/manifests/03-role-bindings.yaml | ||
@kubectl apply -f https://raw.githubusercontent.com/openshift/elasticsearch-operator/release-${ES_OPERATOR_VERSION}/manifests/04-crd.yaml -n ${ES_OPERATOR_NAMESPACE} | ||
@kubectl apply -f https://raw.githubusercontent.com/openshift/elasticsearch-operator/release-${ES_OPERATOR_VERSION}/manifests/05-deployment.yaml -n ${ES_OPERATOR_NAMESPACE} | ||
@kubectl set image deployment/elasticsearch-operator elasticsearch-operator=quay.io/openshift/origin-elasticsearch-operator:${ES_OPERATOR_VERSION} -n ${ES_OPERATOR_NAMESPACE} |
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 like this more than sed, however this is not perfect either.
The manifest should have the correct version in the branch. I have submitted a PR for it openshift/elasticsearch-operator#175
Codecov Report
@@ Coverage Diff @@
## master #537 +/- ##
=======================================
Coverage 91.97% 91.97%
=======================================
Files 69 69
Lines 3501 3501
=======================================
Hits 3220 3220
Misses 196 196
Partials 85 85 Continue to review full report at Codecov.
|
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
Only difference vs using sed is that it has two deployments until the one that was modified terminates, but shouldn't be a big problem.
thanks @objectiser. The es-operator deploys quite quickly it shouldn't cause problems. |
Related to #481
Replaces #535
On the team meeting we agreed to use pinned es-operator version to avoid breaking us.
Signed-off-by: Pavol Loffay ploffay@redhat.com