Releases: ManagedKube/kubernetes-ops
v0.1.23
v0.1.22 - GCP Firewall rules for Prometheus
When using the Prometheus Operator with a Private GKE cluster, the GKE Kubernetes masters do not have full access to your worker nodes. The problem is that on a prometheus-operator update, the Kubernetes masters needs to reach out to prometheus for some webhook validations and by default the port is not open. This opens the port 8443 on the worker nodes. This also opens port 6443 for prometheus adapter usage when using custom metrics for HPA.
Example usage: https://github.com/ManagedKube/kubernetes-ops/blob/master/tf-environments/gcp/dev/firewall-rules/prometheus/terragrunt.hcl
v0.1.21 - Removing Flux Items
The Flux items are in it's own repository now: https://github.com/ManagedKube/kubernetes-common-services
v0.1.20 - Fixing Kops topology indentation
This release has a fix for the kops topology indentation. It was indented one over which means this setting was not taking affect.
v0.1.19 - Flux Release
This release adds in Weaveworks Flux usage.
The problem: In this repo there are no CI/CD pipelines for deploying any of the Helm charts. Each of the Helm charts has a Makefile but that still means a local deployment. The problem was really which CI system should the deployment pipeline be created in? Everyone has their own fav and security requirements which made it hard to make a common thing that everyone could use. That is until Flux came out. I think Flux is a very good common ground. It runs in cluster so you don't need a Jenkins server or open a hole for a SaaS CI system like Github Action or CodeFresh to reach in. This also gives us a complete GitOps workflow for updating and deploying out changes which is awesome!
What this release has:
- Helm deployment for Flux
- Helm deployment for the Flux Helm Operator
- Example usage for nginx-ingress and Prometheus Operator
v0.1.18 - Support for GKE Regional an Zonal Cluster Type
We have only allowed regional clusters so far because it handle most of the use cases. However, GCP will now charge $0.10/hour for a regional cluster and if you have one zonal cluster it is free.
This adds support to allow you to specify if you want a regional or zonal cluster.
v0.1.17 - GCP/GKE Update
GKE Update. A major update to the GCP/GKE infrastructure and CIDR blocks.
v0.1.16 - Folder re-structuring [FINAL]
One more folder restructuring. This removes the need to duplicate environment folder names and thought through the work flow a bit more. this FINAL one is a lot cleaner with less repeated items.
v0.1.15 - Re-organizing the Terragrunt AWS Directory Structure
This set of changes aligns with the how the GCP Terragrunt environment folders are layed out. This sets it up so that there are less env name variables to change in the Terragrunt files by using the directory structure for that purpose instead. This seems to be easier to use and see.
The docs on the easy way and the harder way are also updated with this new directory structure.
v0.1.14 - AWS Transit Gateway Network Example
Using Terraform to build a multi-region transit network to connect various VPCs together into a routing domain.
Main README.md and usage: https://github.com/ManagedKube/kubernetes-ops/tree/v0.1.14/tf-modules/aws/networks
Terraform modules: https://github.com/ManagedKube/kubernetes-ops/tree/v0.1.14/tf-modules/aws/networks
Terraform example values: https://github.com/ManagedKube/kubernetes-ops/tree/v0.1.14/tf-environments/infrastructure/aws/transit-gateway
Diagrams: https://github.com/ManagedKube/kubernetes-ops/tree/v0.1.14/docs/aws-transit-gateway