chore: bump controller image to 20a1a90#100
Merged
Conversation
…only ports) Picks up the post-#99 controller binary: - new SeiNodeDeployment.status.internalService field - per-deployment ClusterIP Service with the stateless HTTP port set (rpc/evm-http/rest only — evm-ws and grpc deliberately excluded) - internal Service lifecycle is independent of .spec.networking Unblocks the autobake workflow (platform repo, M2b) which reads status.internalService.name to dial the chain's RPC. Image: 189176372795.dkr.ecr.us-east-2.amazonaws.com/sei/sei-k8s-controller:20a1a9038725109d434f3940797200afaf75aa44 sha256:05ee5a60d3541c10e0409086381284a1e1695aabd771a14b049de170e1ac0a37 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bdchatham
added a commit
that referenced
this pull request
Apr 17, 2026
Controller pods crash on startup with:
Failed to initialize OTel MeterProvider
error: building OTel resource: conflicting Schema URL:
https://opentelemetry.io/schemas/1.40.0 and
https://opentelemetry.io/schemas/1.26.0
resource.Merge rejects merging resources whose schema URLs differ.
resource.Default() reports schema v1.40.0 (embedded in the SDK at
v1.43.0), while cmd/telemetry.go hardcoded semconv/v1.26.0 as the
schema for the custom resource overlay.
Bump the semconv import to v1.40.0 so the two schema URLs agree.
All three symbols in use here (semconv.SchemaURL, ServiceName,
ServiceVersion) are stable across semconv versions — drop-in
substitution.
Unblocks the controller image bump that #100 landed. Post-#99
controller pods stop CrashLoopBackOff and roll out cleanly, which
in turn unblocks SeiNodeDeployment.status.internalService for the
autobake workflow.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bdchatham
added a commit
that referenced
this pull request
Apr 17, 2026
Controller pods crash on startup with:
Failed to initialize OTel MeterProvider
error: building OTel resource: conflicting Schema URL:
https://opentelemetry.io/schemas/1.40.0 and
https://opentelemetry.io/schemas/1.26.0
resource.Merge rejects merging resources whose schema URLs differ.
resource.Default() reports schema v1.40.0 (embedded in the SDK at
v1.43.0), while cmd/telemetry.go hardcoded semconv/v1.26.0 as the
schema for the custom resource overlay.
Bump the semconv import to v1.40.0 so the two schema URLs agree.
All three symbols in use here (semconv.SchemaURL, ServiceName,
ServiceVersion) are stable across semconv versions — drop-in
substitution.
Unblocks the controller image bump that #100 landed. Post-#99
controller pods stop CrashLoopBackOff and roll out cleanly, which
in turn unblocks SeiNodeDeployment.status.internalService for the
autobake workflow.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Picks up the post-#99 controller binary that introduced the
SeiNodeDeployment.status.internalServicefield and the per-deployment ClusterIP Service for stateless in-cluster access.What changes in-cluster
SeiNodeDeploymentcontroller starts provisioning a per-deployment{name}-internalClusterIP Service selecting all child node pods (rpc/evm-http/rest ports only — stateful protocols deliberately excluded)..status.internalService.{name,namespace,ports.*}is now populated..spec.networking-driven external exposure.Why
Unblocks the autobake workflow in
sei-protocol/platform(M2b) which reads.status.internalService.nameto dial the chain's RPC.Image
Verified in ECR via
aws ecr describe-images.🤖 Generated with Claude Code