Skip to content
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.

Nested support #54

Closed
kfox1111 opened this issue Feb 26, 2023 · 2 comments · Fixed by #117
Closed

Nested support #54

kfox1111 opened this issue Feb 26, 2023 · 2 comments · Fixed by #117
Labels
enhancement New feature or request

Comments

@kfox1111
Copy link
Contributor

Some organizations will have a root spire server and then want to bind their K8s clusters to it. The chart should support having an upstream spire server.
@kfox1111
Copy link
Contributor Author

kfox1111 commented Feb 26, 2023 •
edited
Loading

See prototype at: #46

@kfox1111
Copy link
Contributor Author

Its working now. Should be ready for review.

@marcofranssen marcofranssen added this to the Nested spire support milestone Mar 2, 2023
@kfox1111 kfox1111 mentioned this issue Mar 13, 2023
Merged
@marcofranssen marcofranssen added the enhancement New feature or request label Mar 17, 2023
@faisal-memon faisal-memon modified the milestones: 0.7.0, 0.8.0 Apr 4, 2023
@faisal-memon faisal-memon removed this from the 0.8.x milestone May 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support Nested Spire with External Agent spiffe/helm-charts
3 participants
@marcofranssen @kfox1111 @faisal-memon