Closed davtex closed 1 month ago
CCOCTL fails to complete the OIDC configuration when creating setting S3 buckets with "--create-private-s3-bucket" on AWS where the AWS S3 policy setting at the Account level to prevent public access to S3 Buckets, and where buckets are created with public access blocked by default. This issue causes the OIDC deployment to terminate due to the attempt to set the S3 bucket policy to block public access as requested by this setting. Is there a possibility to have the CCOCTL code status the S3 Bucket public access setting prior to setting the policy so has not to terminated OIDC deployment if the bucket is already configure to deny public access?
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
Hi,
I am currently working on implementing STS with Cloudfront in our in-house tool for deploying new clusters. I am currently using 4.13.
Everything works when I run ccoctl the first time:
All manifests are created together with correct cluster-authentication-02-config.yaml :
However when I run the same command again (e.g. because installation failed for whatever reason), following happens:
First run logs:
Second run logs:
Problem: ccoctl seems to ignore "--create-private-s3-bucket" flag when S3 bucket already exists and generates incorrect manifest
Expectation: When "--create-private-s3-bucket" is set and S3 bucket exists, I would expect ccoctl to query AWS for associated Cloudfront instance and generate "cluster-authentication-02-config.yaml" manifest with correct value.