Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Adding a status condition for workload identity #668

Closed
grac3gao-zz opened this issue Mar 18, 2020 · 0 comments · Fixed by #714
Closed

Adding a status condition for workload identity #668

grac3gao-zz opened this issue Mar 18, 2020 · 0 comments · Fixed by #714
Labels
area/security kind/cleanup Internal cleanup (tech debt, etc) without customer impact, but affects developer velocity. kind/feature-request New feature or request priority/2 Nice to have feature but doesn't block current release defined by release/*

Comments

@grac3gao-zz
Copy link
Contributor

Problem
We need a status condition for objects for workload identity. When workload identity wasn't properly set, it will be marked.
If the user is not using workload identity (using secret), the status type WorkloadIdentityReady should be unknown. This status will be not included in condset, so that the unknown status will not affect the whole condition to be ready.
This condition should be set in channel and all sources.

Exit Criteria
Adding a status condition for workload identity

@grac3gao-zz grac3gao-zz added the kind/feature-request New feature or request label Mar 18, 2020
@nachocano nachocano added priority/2 Nice to have feature but doesn't block current release defined by release/* kind/cleanup Internal cleanup (tech debt, etc) without customer impact, but affects developer velocity. area/security labels Mar 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/security kind/cleanup Internal cleanup (tech debt, etc) without customer impact, but affects developer velocity. kind/feature-request New feature or request priority/2 Nice to have feature but doesn't block current release defined by release/*
Projects
None yet
2 participants