adr-0054 Allow Application Developer write access to Endpoints and EndpointSlices after Proper Risk Acceptance

[raviranjanelastisys]

⚠️ IMPORTANT ⚠️: This is a public repository. Make sure to not disclose:

• personal data beyond what is necessary for interacting with this Pull Request;
• business confidential information, such as customer names.

Quality gates:

• I'm aware of the Contributor Guide and did my best to follow the guidelines.
• I'm aware of the Glossary and did my best to use those terms.

[lucianvlad]

Please increment the adr number as now we have 2 adr's with 0053

• adr:0053 Observability data for platform services
• adr-0053: Allowance of low vulnerability CVEs

[raviranjanelastisys]

Please increment the adr number as now we have 2 adr's with 0053

• adr:0053 Observability data for platform services
• adr-0053: Allowance of low vulnerability CVEs

Agreed, corrected :)

[cristiklein]

Cool that we catch up with ADRs! I really value that we systematically capture complex discussion in a way that ensure internal and external alignment.

I see two high-level issues with this ADR:

First, this feels way too broad and risk sending the wrong message to people outside the project. This ADR should only address Endpoints and EndpointSlices.

Can you downscope the ADR accordingly?

Second, the decision should really include "after Proper Risk Acceptance" already in the title, as we did with Only allow Ingress Configuration Snippet Annotations after Proper Risk Acceptance.

Can you adjust the ADR accordingly?

Thanks!

[raviranjanelastisys]

Can you downscope the ADR accordingly?

Thanks @cristiklein I agree with you :) , It makes sense to limit to Endpoints and EndpointSlices after Proper Risk Acceptance. I have updated the ADR accordingly :)

[cristiklein]

This reads better now, but I made a few suggestions for how to make it shine. 😄

Thanks!

[raviranjanelastisys]

This reads better now, but I made a few suggestions for how to make it shine. 😄

Thanks!

Thanks @cristiklein I updated the ADR accordingly :)
@lucianvlad Looks like your approval is needed before merge too :)