Repository navigation
Add draft posts: private EKS day 2, Tailscale access, upgrades and audit findings - #9
Merged
Merged
Conversation
… findings Four follow-ups to the private EKS + Argo CD post, all marked draft: true so merging doesn't publish them: - Day 2 on a private EKS cluster: AWS Load Balancer Controller, external-dns and External Secrets via Pod Identity and Argo CD, plus a comparison of human access options (SSM recommended). - Cluster access for a growing team with Tailscale: the Tailscale operator's API server proxy and subnet router, tailnet policy in Terraform, and workload identity federation so neither CI nor the operator stores a secret. - EKS upgrades without the drama: support windows and cost, upgrade order, upgrade insights from CI on a private cluster, and rollback. - What we find when we audit a Kubernetes platform: ten common findings with a check and smallest fix for each. Each has a generated hero image with its source SVG alongside.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Four new blog posts that follow on from Bootstrapping a private EKS cluster with Argo CD. All are marked
draft: true, so merging this doesn't publish anything. They only show up innpm run dev./blog/private-eks-day-2//blog/eks-upgrades-without-drama//blog/platform-audit-findings//blog/private-eks-tailscale/Each one has a generated hero image (
src/assets/blog/generated/*.jpg) with its source SVG committed alongside, following the pattern from the first EKS post.Why
Before publishing
main. The Day 2 and Tailscale code exists only on a localday-2-add-onsbranch ofHeyalSolutions/eks-private-argocd-bootstrapand hasn't been pushed yet. It needs merging before these posts go live, or the file links will 404.<!-- TODO -->comments where real client anecdotes or numbers would help. All the findings are written generically.tailscale.com/cap/kubernetesgrant syntax against Tailscale's docs, and whether the CI identity needs to owntag:k8s-operatorto create the operator's federated identity. The Terraform validates, but it hasn't been applied.Checked
npm run buildpasses. Drafts are excluded from the build.