Repository navigation
fix(tailscale): restore OCI Argo egress proxy - #86
Merged
Merged
Conversation
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
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.
Summary
OCI Argo can once again provision the Tailscale egress proxy used to reach the remote Unraid Kubernetes API. The proxy was requesting tags that the configured OCI OAuth client is not permitted to assign, leaving its backing service without a DNS record and every
unraid-labchild unable to compare.The OCI override now uses the operator-owned tag that is already authorized. This restores the remote-registration path without changing credentials or manually patching ESO-owned resources.
Validation
1.102.3with the layered OCI values;PROXY_TAGS=tag:k8s-operator.pre-commitchecks: yamllint and gitleaks passed.