REQUEST: New integration for kubernetes

[ameukam]

Organization or Repo

kubernetes

Name of integration

Okta

Link to integration website

https://developer.okta.com/docs/guides/social-login/github/main/

Describe what is attempting to be accomplished

Use GitHub as a Identity provider for Okta.

The k8s infra SIG would like to use GitHub as an identity provider to allow authentication to different infrastructure providers managed by the SIG.

We currently target this integration with AWS but it's possible to integrate more platforms (Azure, Equinix, etc...)

Additional context for request

No response

[ameukam]

/assign @kubernetes/owners

cc @jeefy

[ameukam]

FYI @dims /sig k8s-infra /priority important-longterm

[dims]

yes please!

[mrbobbytables]

I am good with that 👍

[cblecker]

How are you planning on locking this down? Will users in Okta need to be pre-created?

[ameukam]

How are you planning on locking this down? Will users in Okta need to be pre-created?

It's not required to pre-create users. I can leverage SCIM to sync github users id to ensure authn.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[ameukam]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jeefy]

/remove-lifecycle stale

@ameukam @upodroid Where were we at with this? We've got it tied into other things already correct?

[ameukam]

It's still unclear how we want to do this. Closing this for the moment.

/close

[k8s-ci-robot]

@ameukam: Closing this issue.

In response to this:

It's still unclear how we want to do this. Closing this for the moment.

/close

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.