Skip to content

Remove duplicate pl-oauth-config ConfigMap from public cloud deps - #2411

Merged
vihangm merged 1 commit into
pixie-io:mainfrom
NopeCharon:remove-duplicate-oauth-configmap
Oct 25, 2026
Merged

vihangm merged 1 commit into
pixie-io:mainfrom
NopeCharon:remove-duplicate-oauth-configmap

Conversation

@NopeCharon

Copy link
Copy Markdown
Contributor

Summary: Remove the duplicate pl-oauth-config ConfigMap from the public cloud deps

pl-oauth-config is defined twice with identical data: in k8s/cloud_deps/public/configs.yaml and in k8s/cloud/base/ory_auth/oauth_config.yaml. The self-hosted install applies cloud_deps first and cloud afterwards, so the cloud_deps copy is always overwritten and never takes effect, and nothing in cloud_deps consumes it (only the auth server and cloud proxy in k8s/cloud do). The dev cloud_deps overlay already relies solely on the ory_auth definition.

The duplicate breaks users who combine the released cloud_deps.yaml and cloud.yaml bundles in a single kustomization, as reported in the issue:

may not add resource with an already registered id: ConfigMap.v1.[noGrp]/pl-oauth-config.plc

This PR drops the ConfigMap from cloud_deps and moves its explanatory comment about the supported providers to the ory_auth definition, which is the one that is actually deployed.

Relevant Issues: Fixes #1840

Type of change: /kind bug

Test Plan: Built k8s/cloud_deps/public and k8s/cloud/public with kustomize v5.4.3 the same way ci/cloud_build_release.sh does, and put both outputs in a single kustomization as in the issue. On main this fails with the error above; with this change it builds successfully, cloud_deps.yaml no longer contains pl-oauth-config, and the rendered pl-oauth-config from cloud.yaml is unchanged.

Changelog Message:

Removed the duplicate `pl-oauth-config` ConfigMap from the self-hosted Pixie Cloud `cloud_deps.yaml` so it can be combined with `cloud.yaml` in a single kustomization.

The pl-oauth-config ConfigMap was defined both in
k8s/cloud_deps/public/configs.yaml and in
k8s/cloud/base/ory_auth/oauth_config.yaml, with identical data. The
self-hosted install applies cloud_deps first and cloud afterwards, so
the copy in cloud_deps is always overwritten and never takes effect.
None of the cloud_deps resources consume it either; only the auth server
and cloud proxy in k8s/cloud do.

The duplicate also breaks anyone combining the released cloud_deps.yaml
and cloud.yaml bundles in a single kustomization:

  may not add resource with an already registered id:
  ConfigMap.v1.[noGrp]/pl-oauth-config.plc

Drop the ConfigMap from cloud_deps and carry its explanatory comment over
to the ory_auth definition, which is the one that is actually deployed
(and the only one used by the dev cloud_deps overlay as well).

Fixes pixie-io#1840

Signed-off-by: NopeCharon <[email protected]>
@NopeCharon
NopeCharon requested a review from a team as a code owner October 25, 2026 09:53
@NopeCharon
NopeCharon deployed to pr-actions-approval October 25, 2026 09:53 — with GitHub Actions Active
@vihangm
vihangm merged commit 3e3350f into pixie-io:main Oct 25, 2026
20 checks passed

This branch was successfully deployed

1 active deployment
pr-actions-approval — b48be27c Deployed Oct 25, 2026 by NopeCharon via authorize #3141
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

duplicate ConfigMap pl-oauth-config in cloud_deps.yaml file

2 participants