Update getting-started-k8s.md

[cccsss01]

New updated tutorial with latest helm chart. Need to wait for PR #119 & PR #120 to be accepeted in spiffe/spiffe-tutorials

[netlify]

👷 Deploy request for spiffe pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	28cbaed

[elinesterov]

This is awesome! Thank you so much for it! I think it would be nice to have Helm chart installation as a first option to use spire with k8s, but I would also leave the pure yaml files installation there as well (it probably would need some more massaging and updates.

[cccsss01]

I have PR #19 and #20 to spire-tutorials to create a new folder quickstart-helm, to leaving the original quickstart in place. Still want the original separated? Helm manifest put's it all together.

[amoore877]

fixing DCO check should be fairly straight forward, though you may need to force push :)

thanks for bringing this up to helm charts sync.
there is not an overlap in reviewers for spiffe.io vs helm-charts maintainers, but I'd suspect we primarily do want the helm-chart maintainers review and then general formatting/clarity review by spiffe.io

Looking forward to your continued contributions 🥳

[elinesterov]

Hey @cccsss01 do you mind fixing DCO? Should be straightforward to do this.

[elinesterov]

@cccsss01 I'm not sure that you are referencing to a correct PRs

[cccsss01]

@cccsss01 I'm not sure that you are referencing to a correct PRs

Correct, Looks like the PR's are referencing the wrong project

I haven't been able to put time into this but it's on my list.

[quintessence]

PRs should be:

• New directory to host a new helm tutorial/quickstart spire-tutorials#119
• Updated client-deployment.yaml spire-tutorials#120

(Note: these are not merged, just the correct links)

[mchurichi]

hey @cccsss01 thank you for working on this! do you still have some cycles to finish these PRs? they need the DCO to be fixed and probably a few more changes as the charts have split since this PR. I'd also support the suggestion of keeping the original k8s tutorial and manifests, and adding this as an additional preferred option.

@kfox1111 and other maintainers of the hardened helm chart may also be willing to help with the tutorials and manifests

[kfox1111]

@mchurichi Would it make sense to rename the original tutorial/manifests as something like "SPIRE from Scratch on Kubernetes"?

Its still quite useful for those wanting to learn how it all works, but not as configurable / tested so "some assembly required" and not as preferred a recommendation?

[mchurichi]

@mchurichi Would it make sense to rename the original tutorial/manifests as something like "SPIRE from Scratch on Kubernetes"?

Its still quite useful for those wanting to learn how it all works, but not as configurable / tested so "some assembly required" and not as preferred a recommendation?

@kfox1111 yes, definitely! we should rename the old tutorial to make it clear that it's not the recommended way anymore.

[quintessence]

Thought - if this is removing an outdated tutorial, perhaps removing the "old way" is the way to go? To prevent confusion and help people with onboarding.

[cccsss01]

I think this should be closed in favor of what keven fox has done.

[kfox1111]

Seems like the consensus is to move the old getting started to a new name involving "from scratch" and then make the existing page just a small blurb helping the user choose links something like:

1. the hardened chart install doc
2. the from scratch quickstart
3. When the flex chart works, the flex quickstart

?

Should we close this pr and start a new one for that work, or rework this one to do those things intead?

[elinesterov]

Just my 2 cents here:
I helped to kick off the helm chart work, and I thought that it would be a quick start guide for a Kubernetes because you can do helm install spire. I don't think we should throw away the existing k8s quick start guide. It should be renamed to something like Running SPIRE on k8s in a hard way or something similar. For people who want to understand how to run it in the details using k8s yaml files without getting through the complexities of helm charts.

[v0lkan]

Closing this PR.

I agree with @elinesterov here.

We should restructure the site with two separate guides (hard way, and helm way)

I'll create a separate issue and reference this ticket.

Thanks for all the hardwork in adding the necessary steps.
Rest assured, they won't get wasted.