Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Goole WIF Support for Tecton-Caches #71

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pramodbindal
Copy link
Contributor

No description provided.

SRVKP-6522 - Enable Google WIF Support

SRVKP-6522 - Fix Lint
projected:
sources:
- serviceAccountToken:
audience: https://iam.googleapis.com/projects/272779626560/locations/global/workloadIdentityPools/openshift-pool/providers/opeshift-wif
Copy link
Member

Choose a reason for hiding this comment

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

Can you please put this in conventional format for k8s and OpenShift?

Copy link
Member

@khrm khrm Oct 8, 2024

Choose a reason for hiding this comment

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

Some of our customers will complain that WIF isn't properly supported if do this. We already have a mail on this for OpenShift Logging.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

They way it was setup audience is getting generated like this only. Will check if this can be simplified

Copy link
Member

Choose a reason for hiding this comment

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

Yes, that and location where we project should also be similar.

@@ -0,0 +1,62 @@
#!/usr/bin/env bash
set -x
Copy link
Member

Choose a reason for hiding this comment

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

I think we should have this script in e2e section.

Copy link
Contributor Author

@pramodbindal pramodbindal Oct 8, 2024

Choose a reason for hiding this comment

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

For now we dont have have e2e for GCS and AWS as that will require test accounts configuration in Github action. once that is done we can move it to e2e.

@@ -0,0 +1,34 @@
---
Copy link
Member

Choose a reason for hiding this comment

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

This file should ideally be in example folder.

@@ -70,12 +70,12 @@ spec:
value: $(params.googleCredentialsPath)
Copy link
Member

Choose a reason for hiding this comment

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

This file should be in the config folder. That's how we do it for every other Tekton project.

Copy link
Member

Choose a reason for hiding this comment

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

This can be done in a separate PR.

Copy link
Member

Choose a reason for hiding this comment

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

We now have step actions in two folder - tekton and this.

Should be merged to config.

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.

2 participants