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

Serve Public Certificates like CA Bundles #31

Open
vpnachev opened this issue Jun 4, 2024 · 3 comments · May be fixed by #91
Open

Serve Public Certificates like CA Bundles #31

vpnachev opened this issue Jun 4, 2024 · 3 comments · May be fixed by #91
Assignees
Labels
area/ipcei IPCEI (Important Project of Common European Interest) kind/enhancement Enhancement, improvement, extension priority/2 Priority (lower number equals higher priority)

Comments

@vpnachev
Copy link
Member

vpnachev commented Jun 4, 2024

What would you like to be added:
Capability public certificates like CA bundles to be served by the discovery server. For shoots, it would be nice the current request path pattern to be re-used, e.g. /projects/{projectName}/shoots/{shootUID}/ca-bundles. It would be nice the path to be designed in a way that it can accommodate more use cases in the future.

Why is this needed:
Easy discovery and distribution of the the CA bundles that have to be trusted by clients.

@vpnachev vpnachev added the kind/enhancement Enhancement, improvement, extension label Jun 4, 2024
@gardener-ci-robot
Copy link

The Gardener project currently lacks enough active contributors to adequately respond to all issues.
This bot triages 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
  • Mark this issue as rotten with /lifecycle rotten
  • Close this issue with /close

/lifecycle stale

@gardener-prow gardener-prow bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2024
@abhijith-darshan
Copy link

What would you like to be added: Capability public certificates like CA bundles to be served by the discovery server. For shoots, it would be nice the current request path pattern to be re-used, e.g. /projects/{projectName}/shoots/{shootUID}/ca-bundles. It would be nice the path to be designed in a way that it can accommodate more use cases in the future.

Why is this needed: Easy discovery and distribution of the the CA bundles that have to be trusted by clients.

➕ 1

@gardener-ci-robot
Copy link

The Gardener project currently lacks enough active contributors to adequately respond to all issues.
This bot triages 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

/lifecycle rotten

@gardener-prow gardener-prow bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 13, 2024
@dimityrmirchev dimityrmirchev removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Nov 7, 2024
@JordanJordanov JordanJordanov added priority/2 Priority (lower number equals higher priority) area/ipcei IPCEI (Important Project of Common European Interest) labels Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ipcei IPCEI (Important Project of Common European Interest) kind/enhancement Enhancement, improvement, extension priority/2 Priority (lower number equals higher priority)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants