CI steps fail publishing images and logging into docker

[gdfast]

Component(s)

No response

Describe the issue you're reporting

I've been doing the typical contributor flow of making commits to branches on my fork – https://github.com/gdfast/opentelemetry-operator – and then opening pull requests again the main repo. When I updated PR #3080 today after merging in new upstream changes from the main branch, I got a series of CI failures, including:

• [gdfast/opentelemetry-operator] Publish operator bundle workflow run
• [gdfast/opentelemetry-operator] Publish NodeJS Auto-Instrumentation workflow run
• [gdfast/opentelemetry-operator] Publish operator workflow run
• [gdfast/opentelemetry-operator] Publish Operator OpAMP Bridge workflow run
• [gdfast/opentelemetry-operator] Publish target allocator workflow run

All of these workflows fail at the "Log into Docker.io" step with

Error: Username and password required

A little later, I also got the failure

• [gdfast/opentelemetry-operator] Publish Test E2E images workflow run

which failed in each workflow's Build and push step with

Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/open-telemetry/opentelemetry-operator/e2e-test-app-bridge-server:main: unexpected status from POST request to https://ghcr.io/v2/open-telemetry/opentelemetry-operator/e2e-test-app-bridge-server/blobs/uploads/: 403 Forbidden

My fork was sync'ed to this commit: 1289c63

I acknowledge the OTel Operator is under active development and I may have missed a new setup step that wasn't previously required.

[pavolloffay]

All these workflows are from your fork https://github.com/gdfast/opentelemetry-operator. We don't guarantee that GHA workflows will work in forked repositories.

[jaronoff97]

@pavolloffay i wonder if we should either disable workflows on user forks by default or have it use their repo for pushing images. That being said, idk why we do a push at all for this?

[pavolloffay]

I would not object if someone wants to use generic org-name/repo-name in GHA e.g.

opentelemetry-operator/.github/workflows/publish-autoinstrumentation-java.yaml

Line 37 in 98006c2

ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-java

but I would treat it as a best effort. It's problematic to test and maintain.