Skip to content

[WIP]OCPBUGS-85429: Bump to 1.36.2 - #666

Open
jubittajohn wants to merge 6 commits into
openshift:mainfrom
jubittajohn:bump-1.36.2
Open

[WIP]OCPBUGS-85429: Bump to 1.36.2#666
jubittajohn wants to merge 6 commits into
openshift:mainfrom
jubittajohn:bump-1.36.2

Conversation

@jubittajohn

@jubittajohn jubittajohn commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Updated build tooling to Go 1.26, refreshed platform/component dependencies, and bumped the build-root and RHEL-based images to the OpenShift 5.0 line.
    • Improved OpenAPI spec generation logic for release/image selection and registry authentication fallback.
  • Bug Fixes
    • Updated route validation and host allocation/update to use the standard validation behavior.
    • Corrected OpenAPI name-matching checks for device attribute fields and added the missing node configuration validation entry.
  • Documentation
    • Improved generated deep-copy tooling configuration for API packages.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 27, 2026
@openshift-ci
openshift-ci Bot requested review from bparees and xueqzhan July 27, 2026 20:45
@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

The project baseline is updated to Go 1.26, Kubernetes 1.36.2, and OpenShift 5.0. API-generation metadata, route validation interfaces, quota initialization, and OpenAPI tooling are also updated.

Changes

Platform and API-generation baseline

Layer / File(s) Summary
Release dependency and image baseline
.ci-operator.yaml, go.mod, images/Dockerfile.rhel
Go, Kubernetes, OpenShift, indirect dependencies, replacement mappings, CI images, and RHEL container images are upgraded.
API generation and OpenAPI metadata
hack/openapi-violation.list, hack/update-generated-deep-copies.sh, hack/update-openapi-spec.sh
OpenAPI exceptions, deepcopy generation arguments, release selection, and registry credential selection are updated.

Route and admission behavior

Layer / File(s) Summary
Route validation interface simplification
pkg/route/..., pkg/api/validation/register.go
Route validation and host-assignment functions no longer accept or forward route validation options, including the strategy-specific external-certificate option.
Quota initialization error handling
pkg/cmd/openshift-apiserver/openshiftadmission/plugin_initializer.go
Quota configuration initialization now checks and returns errors before constructing the quota registry.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Suggested reviewers: bparees, xueqzhan

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 12.50% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (14 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed No *_test.go files changed, and none of the changed Go files contain Ginkgo titles (It/Describe/Context/When).
Test Structure And Quality ✅ Passed PASS: No *_test.go or Ginkgo specs were changed; this PR only touches tooling, generated files, and production code, so the test-quality checklist isn’t applicable.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests were added; the PR only changes production/generated code and scripts, and no strict Ginkgo markers were found.
Single Node Openshift (Sno) Test Compatibility ✅ Passed No new Ginkgo e2e tests were added in the touched files; the PR only updates tooling/validation code, and search found no It/Describe/Context/When declarations.
Topology-Aware Scheduling Compatibility ✅ Passed No touched file adds node selectors, affinities, spread constraints, tolerations, or replica placement logic; route changes are admission-only.
Ote Binary Stdout Contract ✅ Passed PASS: The touched process-level files add no stdout writes or logging setup changes; the only os.Stdout reference is unchanged in cmd/openshift-apiserver/main.go.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No new/modified Ginkgo or e2e test files appear in the diff, so there are no IPv4 or disconnected-network assumptions to assess.
No-Weak-Crypto ✅ Passed No new weak-crypto code or secret comparisons were added; the DES/RC4/blowfish strings pre-existed in base vendor/docs, and the touched Go files contain none.
Container-Privileges ✅ Passed The PR tip only changes a shell script; no container/K8s manifests were modified, so none of the listed privilege settings are introduced.
No-Sensitive-Data-In-Logs ✅ Passed No new code logs secrets/PII; the only added echoes print release/image paths and pull-secret file paths, not contents.
Title check ✅ Passed The title clearly identifies the primary change as updating the project to version 1.36.2, which matches the dependency and platform component updates.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@go.mod`:
- Line 177: Update the google.golang.org/grpc dependency in go.mod from v1.79.3
to a version newer than v1.82.1, preserving the existing indirect dependency
declaration.
- Line 210: Remove the forked k8s.io/apiserver replacement from go.mod and
eliminate the matching override in vendor/modules.txt. Before release, use the
approved carry source if one exists; otherwise ensure the forked module is
absent from release artifacts.

In `@hack/update-generated-deep-copies.sh`:
- Line 28: Update the deepcopy-gen invocation in update-generated-deep-copies.sh
to quote both the GOPATH-based generator path and the SCRIPT_ROOT-based
boilerplate path, preserving the existing arguments and generation behavior.

In `@images/Dockerfile.rhel`:
- Around line 7-10: Add a non-root USER directive and a HEALTHCHECK to the
runtime stage of Dockerfile.rhel after the binary COPY instructions and before
ENTRYPOINT; configure the health check to probe the running openshift-apiserver
readiness endpoint and ensure the selected user can execute the entrypoint and
access required files.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

Comment thread go.mod Outdated
Comment thread go.mod
k8s.io/api => k8s.io/api v0.36.2
k8s.io/apiextensions-apiserver => k8s.io/apiextensions-apiserver v0.36.2
k8s.io/apimachinery => k8s.io/apimachinery v0.36.2
k8s.io/apiserver => github.com/jacobsee/kubernetes-apiserver v0.0.0-20260721191758-685ad32f88c0 // temporary: add-carries-to-1.36.2 branch

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Inspect the surrounding go.mod context
nl -ba go.mod | sed -n '190,225p'

# Find any references to the replacement or the fork
rg -n "jacobsee/kubernetes-apiserver|k8s.io/apiserver|temporary: add-carries-to-1.36.2 branch|release approval|provenance|sigstore|cosign" .

# Capture the module replacement details if present elsewhere
git ls-files | rg '(^|/)go\.mod$|(^|/)go\.sum$|(^|/)README|(^|/)docs?/'

Repository: openshift/openshift-apiserver

Length of output: 207


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show the relevant go.mod section using portable tools
sed -n '190,225p' go.mod

echo
echo "---- matches ----"
rg -n "jacobsee/kubernetes-apiserver|k8s.io/apiserver|temporary: add-carries-to-1.36.2 branch|release approval|provenance|sigstore|cosign" .

echo
echo "---- module files ----"
git ls-files | rg '(^|/)go\.mod$|(^|/)go\.sum$|(^|/)README|(^|/)docs?/'

Repository: openshift/openshift-apiserver

Length of output: 50386


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "---- go.mod around replacement ----"
sed -n '205,215p' go.mod

echo
echo "---- replace directives in go.mod ----"
rg -n '^\s*replace\s+.*k8s\.io/apiserver|jacobsee/kubernetes-apiserver|add-carries-to-1\.36\.2' go.mod

echo
echo "---- repo guidance mentions ----"
rg -n 'release approval|provenance|cosign|sigstore|SBOM|supply chain|temporary replacement|fork' README* docs* .github* . 2>/dev/null | head -n 200

Repository: openshift/openshift-apiserver

Length of output: 31041


go.mod:210 — Remove this forked k8s.io/apiserver replacement before release. It redirects the module to github.com/jacobsee/kubernetes-apiserver, and vendor/modules.txt carries the same override. Route it through the approved carry source or keep it out of release artifacts.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@go.mod` at line 210, Remove the forked k8s.io/apiserver replacement from
go.mod and eliminate the matching override in vendor/modules.txt. Before
release, use the approved carry source if one exists; otherwise ensure the
forked module is absent from release artifacts.

Source: Path instructions

Comment thread hack/update-generated-deep-copies.sh Outdated
Comment thread images/Dockerfile.rhel

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
pkg/api/validation/register.go (1)

84-89: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Rename the adapters now that they no longer adapt options.

routeOptionsAdapter and routeUpdateOptionsAdapter are now misleading. Rename them to reflect route validation and update the registration reference accordingly.

Proposed rename
-Validator.MustRegister(&routeapi.Route{}, true, routeOptionsAdapter, routeUpdateOptionsAdapter)
+Validator.MustRegister(&routeapi.Route{}, true, routeValidationAdapter, routeValidationUpdateAdapter)

-func routeOptionsAdapter(route *routeapi.Route) field.ErrorList {
+func routeValidationAdapter(route *routeapi.Route) field.ErrorList {

-func routeUpdateOptionsAdapter(route *routeapi.Route, oldRoute *routeapi.Route) field.ErrorList {
+func routeValidationUpdateAdapter(route *routeapi.Route, oldRoute *routeapi.Route) field.ErrorList {
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@pkg/api/validation/register.go` around lines 84 - 89, Rename
routeOptionsAdapter and routeUpdateOptionsAdapter to names reflecting route
validation and route update validation, respectively, and update every
registration or call-site reference to use the new names consistently.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@pkg/api/validation/register.go`:
- Around line 84-89: Rename routeOptionsAdapter and routeUpdateOptionsAdapter to
names reflecting route validation and route update validation, respectively, and
update every registration or call-site reference to use the new names
consistently.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 2005b6fc-2dbb-4eab-85af-3d791247b15e

📥 Commits

Reviewing files that changed from the base of the PR and between 4760adf and 531222a.

⛔ Files ignored due to path filters (1)
  • pkg/openapi/zz_generated.openapi.go is excluded by !**/zz_generated*
📒 Files selected for processing (6)
  • hack/openapi-violation.list
  • pkg/api/validation/register.go
  • pkg/cmd/openshift-apiserver/openshiftadmission/plugin_initializer.go
  • pkg/route/apis/route/validation/validation.go
  • pkg/route/apiserver/admission/routehostassignment/adapter.go
  • pkg/route/apiserver/registry/route/strategy.go
🚧 Files skipped from review as they are similar to previous changes (1)
  • hack/openapi-violation.list

jubittajohn and others added 5 commits July 27, 2026 17:12
@jubittajohn jubittajohn mentioned this pull request Jul 28, 2026
@jubittajohn jubittajohn changed the title WIP: Bump to 1.36.2 [WIP]OCPBUGS-85429: Bump to 1.36.2 Jul 28, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jul 28, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@jubittajohn: This pull request references Jira Issue OCPBUGS-85429, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary by CodeRabbit

  • Chores
  • Upgraded build tooling to Go 1.26 and refreshed platform components.
  • Updated RHEL-based builder/runtime images and the build-root release image to the OpenShift 5.0 line.
  • Improved quota admission plugin initialization to properly handle configuration creation failures.
  • Bug Fixes
  • Refreshed route validation and host-assignment to use default route validation behavior.
  • Updated OpenAPI naming-match checks for device attribute fields and added a node configuration validation entry.
  • Documentation
  • Improved generated deep-copy tooling configuration for API packages.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

Copy link
Copy Markdown

@jubittajohn: This pull request references Jira Issue OCPBUGS-85429, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

Summary by CodeRabbit

  • Chores
  • Updated build tooling to Go 1.26 and refreshed platform/component dependencies.
  • Upgraded the RHEL-based builder/runtime images and switched the build-root release image to the OpenShift 5.0 line.
  • Improved automation for generating OpenAPI specs and registry auth selection.
  • Bug Fixes
  • Refreshed route validation and host-assignment to rely on default validation behavior (removing custom options plumbing).
  • Updated OpenAPI naming-match checks for device attribute fields and added a missing node configuration validation entry.
  • Documentation
  • Improved generated deep-copy tooling configuration for API packages.
  • Tests
  • Improved quota admission plugin initialization to properly handle configuration creation failures.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@hack/update-openapi-spec.sh`:
- Around line 145-152: Update the OPENSHIFT_VERSION detection probe in
hack/update-openapi-spec.sh to tolerate a grep pipeline with no openshift-X.Y
match under errexit and pipefail. Add the failure suppression to the
grep/head/sed assignment so execution reaches the existing empty-value check and
error message, while preserving successful version detection.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 417345d4-8173-4b4b-8153-fd7036ae80d3

📥 Commits

Reviewing files that changed from the base of the PR and between 64d8f35 and 68e10fc.

📒 Files selected for processing (1)
  • hack/update-openapi-spec.sh

Comment thread hack/update-openapi-spec.sh Outdated
Comment on lines +145 to +152
if [[ -f "${SCRIPT_ROOT}/.ci-operator.yaml" ]]; then
OPENSHIFT_VERSION=$(grep -o 'openshift-[0-9]*\.[0-9]*' "${SCRIPT_ROOT}/.ci-operator.yaml" | head -1 | sed 's/openshift-//')
fi
if [[ -z "${OPENSHIFT_VERSION}" ]]; then
echo "ERROR: Could not detect OpenShift version from .ci-operator.yaml"
echo "Please set OPENSHIFT_RELEASE environment variable manually, e.g.:"
echo " OPENSHIFT_RELEASE=registry.ci.openshift.org/ocp/release:5.0 $0"
exit 1

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Inspect the relevant section of the script
sed -n '132,170p' hack/update-openapi-spec.sh

printf '\n--- shell probe ---\n'
tmpdir="$(mktemp -d)"
cat >"$tmpdir/probe.sh" <<'EOF'
#!/bin/bash
set -euo pipefail

f="$1"
OPENSHIFT_VERSION=""
if [[ -f "$f" ]]; then
  OPENSHIFT_VERSION=$(grep -o 'openshift-[0-9]*\.[0-9]*' "$f" | head -1 | sed 's/openshift-//')
fi
echo "OPENSHIFT_VERSION=${OPENSHIFT_VERSION:-<empty>}"
echo "reached end"
EOF
chmod +x "$tmpdir/probe.sh"

cat >"$tmpdir/match.yaml" <<'EOF'
something openshift-4.16 other
EOF
cat >"$tmpdir/nomatch.yaml" <<'EOF'
something else
EOF

echo "match case:"
bash "$tmpdir/probe.sh" "$tmpdir/match.yaml" ; echo "exit=$?"

echo "no-match case:"
bash "$tmpdir/probe.sh" "$tmpdir/nomatch.yaml" ; echo "exit=$?"

Repository: openshift/openshift-apiserver

Length of output: 1958


🏁 Script executed:

sed -n '132,170p' hack/update-openapi-spec.sh

Repository: openshift/openshift-apiserver

Length of output: 1868


🏁 Script executed:

#!/bin/bash
set -euo pipefail

sed -n '132,170p' hack/update-openapi-spec.sh

tmpdir="$(mktemp -d)"
cat >"$tmpdir/probe.sh" <<'EOF'
#!/bin/bash
set -euo pipefail

f="$1"
OPENSHIFT_VERSION=""
if [[ -f "$f" ]]; then
  OPENSHIFT_VERSION=$(grep -o 'openshift-[0-9]*\.[0-9]*' "$f" | head -1 | sed 's/openshift-//')
fi
echo "OPENSHIFT_VERSION=${OPENSHIFT_VERSION:-<empty>}"
echo "reached end"
EOF
chmod +x "$tmpdir/probe.sh"

cat >"$tmpdir/match.yaml" <<'EOF'
something openshift-4.16 other
EOF
cat >"$tmpdir/nomatch.yaml" <<'EOF'
something else
EOF

echo "match case:"
bash "$tmpdir/probe.sh" "$tmpdir/match.yaml"; echo "exit=$?"

echo "no-match case:"
bash "$tmpdir/probe.sh" "$tmpdir/nomatch.yaml"; echo "exit=$?"

Repository: openshift/openshift-apiserver

Length of output: 1937


Preserve the version-detection fallback.

With errexit and pipefail, a .ci-operator.yaml without an openshift-X.Y match makes the grep pipeline abort before the empty-value check can emit the intended error. Add || true to the probe so the script reaches that branch.

Proposed fix
-      OPENSHIFT_VERSION=$(grep -o 'openshift-[0-9]*\.[0-9]*' "${SCRIPT_ROOT}/.ci-operator.yaml" | head -1 | sed 's/openshift-//')
+      OPENSHIFT_VERSION=$(grep -o 'openshift-[0-9]*\.[0-9]*' "${SCRIPT_ROOT}/.ci-operator.yaml" | head -1 | sed 's/openshift-//' || true)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
if [[ -f "${SCRIPT_ROOT}/.ci-operator.yaml" ]]; then
OPENSHIFT_VERSION=$(grep -o 'openshift-[0-9]*\.[0-9]*' "${SCRIPT_ROOT}/.ci-operator.yaml" | head -1 | sed 's/openshift-//')
fi
if [[ -z "${OPENSHIFT_VERSION}" ]]; then
echo "ERROR: Could not detect OpenShift version from .ci-operator.yaml"
echo "Please set OPENSHIFT_RELEASE environment variable manually, e.g.:"
echo " OPENSHIFT_RELEASE=registry.ci.openshift.org/ocp/release:5.0 $0"
exit 1
if [[ -f "${SCRIPT_ROOT}/.ci-operator.yaml" ]]; then
OPENSHIFT_VERSION=$(grep -o 'openshift-[0-9]*\.[0-9]*' "${SCRIPT_ROOT}/.ci-operator.yaml" | head -1 | sed 's/openshift-//' || true)
fi
if [[ -z "${OPENSHIFT_VERSION}" ]]; then
echo "ERROR: Could not detect OpenShift version from .ci-operator.yaml"
echo "Please set OPENSHIFT_RELEASE environment variable manually, e.g.:"
echo " OPENSHIFT_RELEASE=registry.ci.openshift.org/ocp/release:5.0 $0"
exit 1
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@hack/update-openapi-spec.sh` around lines 145 - 152, Update the
OPENSHIFT_VERSION detection probe in hack/update-openapi-spec.sh to tolerate a
grep pipeline with no openshift-X.Y match under errexit and pipefail. Add the
failure suppression to the grep/head/sed assignment so execution reaches the
existing empty-value check and error message, while preserving successful
version detection.

Comment thread hack/update-openapi-spec.sh Outdated
echo " OPENSHIFT_RELEASE=quay.io/openshift-release-dev/ocp-release:4.22.0-x86_64 $0"
exit 1
# Determine which release image to use.
# Priority: OPENSHIFT_RELEASE env var > RELEASE_IMAGE_LATEST (set by ci-operator) > auto-detect from .ci-operator.yaml

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can OPENSHIFT_RELEASE be assigned in the job invocation instead of baking knowledge of RELEASE_IMAGE_LATEST into this script?

Comment thread hack/update-openapi-spec.sh Outdated
elif [[ -n "${REGISTRY_AUTH_FILE:-}" && -f "${REGISTRY_AUTH_FILE}" ]]; then
if [[ -n "${REGISTRY_AUTH_FILE:-}" && -f "${REGISTRY_AUTH_FILE}" ]]; then
echo "Using pull secret from ${REGISTRY_AUTH_FILE}"
REGISTRY_AUTH_OPTS="--registry-config=${REGISTRY_AUTH_FILE}"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is passing the --registry-config option necessary? It seems like oc itself respects REGISTRY_AUTH_FILE (https://github.com/openshift/oc/blob/a4c90c71ea5562102352df426c71e03381b7a02f/pkg/cli/image/manifest/dockercredentials/auth_resolver.go#L38).

Comment thread hack/update-openapi-spec.sh Outdated
Comment on lines 164 to 167
elif [[ -n "${CLUSTER_PROFILE_DIR:-}" && -f "${CLUSTER_PROFILE_DIR}/pull-secret" ]]; then
echo "Using pull secret from ${CLUSTER_PROFILE_DIR}/pull-secret"
REGISTRY_AUTH_OPTS="--registry-config=${CLUSTER_PROFILE_DIR}/pull-secret"
else

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can remove the CLUSTER_PROFILE_DIR bits if cluster profiles don't include CI registry pull secrets.

@openshift-ci

openshift-ci Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign gangwgr for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci

openshift-ci Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

@jubittajohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/verify 6ab13ff link true /test verify

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants