-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
-
-
Important
When switching tenants using oc project <tenant-name>, the extensions section containing tekton results configuration is removed from the target's context configuration, requiring re-running opc results config set or manually editing ~/.kube/config after every tenant switch. This happens when "switching" to the current tenant.
Steps to reproduce:
$ opc results config view api-path: "" apiVersion: results.tekton.dev/v1alpha2 host: tekton-results-tekton-results.apps.<something.something>.openshiftapps.com insecure-skip-tls-verify: "false" kind: Client token: sha256~<redacted> $ current_tenant=`kubectl config current-context | cut -d/ -f1` $ oc project $current_tenant Already on project "<something>-tenant" on server "https://api.<something.something>.openshiftapps.com:6443". $ opc results config view api-path: "" apiVersion: results.tekton.dev/v1alpha2 host: "" kind: Client token: "" $ oc version Client Version: 4.19.13 Kustomize Version: v5.5.0 Kubernetes Version: v1.30.14 $ kubectl version Client Version: v1.32.1 Kustomize Version: v5.5.0 Server Version: v1.30.14 WARNING: version difference between client (1.32) and server (1.30) exceeds the supported minor version skew of +/-1
