kubernetes-guides
kubernetes-guides copied to clipboard
pulumi
Crosswalk Playbooks and Code for Teams to Manage Kubernetes in Production
As pointed in our [documentation](https://www.pulumi.com/docs/guides/crosswalk/kubernetes/app-services/#nginx-ingress-controller), we use `new k8s.helm.v3.Chart(...);`. However, the code in this guide uses `new k8s.helm.v2.Chart(...);`. This PR calls `k8s.helm.v3.Chart()` where applicable and updates how the back-end service...
As identified in https://github.com/pulumi/pulumi-azuread/issues/226, we need to ensure that the code for AzureAD is updated to match that of 5.x.x where there were breaking changes
## Hello! - Vote on this issue by adding a 👍 reaction - If you want to implement this feature, comment to let us know (we'll work with you on...
The basic idea in our model is that the user will bootstrap infrastructure with the following series of actions: 1. Create an account on one of the major cloud providers....
Networking and security infrastructure like (in the case of AWS) VPCs and SecurityGroups have significant security implications in their setup, and the blast radius of changes to this plane are...
Currently `@pulumi/eks` requires very expansive permissions: - Create/delete permissions for IAM Roles, RolePolicyAttachments, InstanceProfile, _etc_. - Create/delete permissions for SecurityGroup and SecurityGroupRule. - Create/delete permissions for various EC2 resource types,...
README.md Step 4 and config.ts Pulumi key names do not match. --- **README.md**: Step 4, config set examples $ pulumi config set k8s-gke-cluster:**identityStackRef** myUser/k8s-gcp-identity/dev-1573589109 $ pulumi config set k8s-gke-cluster:**infraStackRef** myUser/k8s-gcp-infra/dev-1573589378...
KtPW has a bunch of scripts that make it easy to integrate with CI systems, but no specific guidance on how to accomplish this.
Is it in scope for this project to also describe dev, staging, and prod workflows? For the moment, (I believe) this repo suggests only a PR -> prod workflow. Assuming...
There is a set of systems components that are considered industry standard in Kubernetes clusters. We should change the KtPW examples to have tunable, prod-first deployments of these things.