-
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
Updated Operator SDK to v0.18.2 #1126
Updated Operator SDK to v0.18.2 #1126
Conversation
1e03bf0
to
676c3b7
Compare
Codecov Report
@@ Coverage Diff @@
## master #1126 +/- ##
=======================================
Coverage 88.22% 88.22%
=======================================
Files 86 86
Lines 5350 5351 +1
=======================================
+ Hits 4720 4721 +1
Misses 466 466
Partials 164 164
Continue to review full report at Codecov.
|
afbda92
to
c56ce19
Compare
Apparently, the coverage change is related to the skipping of the ingress test. |
@@ -259,7 +259,7 @@ kafka: deploy-kafka-operator | |||
@kubectl create namespace $(KAFKA_NAMESPACE) 2>&1 | grep -v "already exists" || true | |||
@curl --fail --location $(KAFKA_EXAMPLE) --output deploy/test/kafka-example.yaml --create-dirs | |||
@sed -i 's/size: 100Gi/size: 10Gi/g' deploy/test/kafka-example.yaml | |||
@kubectl -n $(KAFKA_NAMESPACE) apply --dry-run=client -f deploy/test/kafka-example.yaml | |||
@kubectl -n $(KAFKA_NAMESPACE) apply --dry-run=true -f deploy/test/kafka-example.yaml |
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.
@kevinearls I think you added this flag in the past. Not sure where this option is parsed, but it currently fails with my client/server combination. I got it working by setting it to client
, but wanted to check with you whether this is indeed the correct value.
For reference, here are the versions I'm using:
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0-4-g38212b5", GitCommit:"d038424d6d4f1cc39ad586ac0d36dac3a7a37ceb", GitTreeState:"clean", BuildDate:"2020-06-16T03:29:46Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:43:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
- 'update' | ||
- 'delete' | ||
- 'watch' | ||
- create |
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 change is mainly to reduce the diff between new operators and this operator, in an attempt to make it easier to compare what changed between SDK versions.
The new list contains patch
, which the old list didn't. Apart from that, it's only ordering and formatting changes.
@@ -41,8 +41,8 @@ func (suite *AllInOneTestSuite) SetupSuite() { | |||
require.FailNow(t, "Failed in prepare") | |||
} | |||
fw = framework.Global | |||
namespace, _ = ctx.GetNamespace() |
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.
@kevinearls heads up: GetNamespace
actually creates a new namespace (!!), which fails during runtime as the namespace already exists. Behind the scenes, GetNamespace
calls GetID
to obtain the namespace's value, hence this change.
osv1 "github.com/openshift/api/route/v1" | ||
osv1sec "github.com/openshift/api/security/v1" | ||
framework "github.com/operator-framework/operator-sdk/pkg/test" | ||
"github.com/operator-framework/operator-sdk/pkg/test/e2eutil" | ||
"github.com/sirupsen/logrus" | ||
"github.com/stretchr/testify/assert" | ||
"github.com/stretchr/testify/require" | ||
"golang.org/x/net/context" |
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 seems to be added via 5c37d2d , but I guess this was supposed to be context
instead. Just wanted to confirm with you if you really meant this old library, or if we can safely change it to use the stdlib's context
.
@jpkrohling I am getting a failure running E2E tests on an OCP cluster, although strangely it's not 100% clear what is failing or why. I will work on this more later today. |
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 a couple of clarifications.
deploy/olm-catalog/jaeger-operator/1.18.1/jaeger-operator.v1.18.1.clusterserviceversion.yaml
Show resolved
Hide resolved
@@ -153,11 +153,11 @@ type Jaeger struct { | |||
// +k8s:openapi-gen=true | |||
type JaegerCommonSpec struct { | |||
// +optional | |||
// +listType=set | |||
// +listType=atomic |
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.
Why these changes?
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.
There was a change in how OpenAPI and the generated resources would validate the values. I don't remember exactly the reason, as this is something I faced during the upgrade of the OpenTelemetry Operator as well: https://github.com/open-telemetry/opentelemetry-operator/pull/24/files#diff-0f1140984003d7bcbaddb3717895a48d
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.
ok 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 some nits.
Does this PR pass the full e2e tests including e2e-tests-self-provisioned-es
on OCP?
@@ -197,6 +197,7 @@ func (b *Background) detectKafka(ctx context.Context, apiList *metav1.APIGroupLi | |||
|
|||
func (b *Background) detectClusterRoles(ctx context.Context) { | |||
tr := &authenticationapi.TokenReview{ | |||
ObjectMeta: metav1.ObjectMeta{Name: "jaeger-operator-TEST"}, |
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.
leftover?
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.
No, this is actually required now, otherwise it fails to validate ("token review has to have a name" or something...)
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.
Could this cause any issues when there are multiple operands in the same namespace or multiple operators in the cluster?
I found a few problems with tests:
|
4f04da8
to
ef1e48e
Compare
Fixes jaegertracing#1125 Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Signed-off-by: Kevin Earls <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
ef1e48e
to
de8e716
Compare
@pavolloffay said:
I think those are the ones that @kevinearls mentioned a few minutes ago and fixed in his branch. I cherry-picked his commit and added to this PR. I also addressed the other comments. The only open comment is about the change from |
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
@jpkrohling @pavolloffay I did a rerun on an OCP 4.4 cluster and all tests have passed, including the self provisioned es tests. |
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, tests are now passing on OCP 4.4
namespace, _ = ctx.GetNamespace() | ||
require.NotNil(t, namespace, "GetNamespace failed") | ||
namespace = ctx.GetID() | ||
require.NotNil(t, namespace, "GetID failed") |
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.
Should these be NotEmpty now? But I'm not sure it can fail at this point
Fixes #1125
Signed-off-by: Juraci Paixão Kröhling [email protected]