NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #2569 by repository stars
Latest stable
v0.19.1
Last release 14 days ago
04 Nov 2026
Release timing varies
gaps range from 9 days to 8 months
Nearly every release is documented
notes for 58 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
172 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
This adds support for skipping the specific components in the sync-core-components command. Review the updated command docs (kubergrunt eks sync-core-
eks sync-core-componentsThis adds support for skipping the specific components in the sync-core-components command. Review the updated command docs (kubergrunt eks sync-core-components --help) for more info.
https://github.com/gruntwork-io/kubergrunt/pull/128
This adds support for Kubernetes version 1.20 in the sync-core-components command. In turn, support for Kubernetes 1.14 and 1.15 has been dropped.
eks sync-core-componentsThis adds support for Kubernetes version 1.20 in the sync-core-components command. In turn, support for Kubernetes 1.14 and 1.15 has been dropped.
https://github.com/gruntwork-io/kubergrunt/pull/127
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This introduces the eks drain subcommand which can be used to cordon and drain all the workers that are associated with the provided AWS Auto Scaling
eks drain [NEW]This introduces the eks drain subcommand which can be used to cordon and drain all the workers that are associated with the provided AWS Auto Scaling Groups. Refer to the command docs for more information.
https://github.com/gruntwork-io/kubergrunt/pull/126
Nothing published for this version
All commands that require AWS access will now properly support credentials configuration defined in ~/.aws/config.
All commands that require AWS access will now properly support credentials configuration defined in ~/.aws/config.
Special thanks to @jtdoepke for their contribution!
https://github.com/gruntwork-io/kubergrunt/pull/123
The eks oidc-thumbprint command now supports HTTP proxies.
eks oidc-thumbprintThe eks oidc-thumbprint command now supports HTTP proxies.
Special thanks to @DanielRis for their contribution!
https://github.com/gruntwork-io/kubergrunt/pull/124
Starting this release, we will publish darwin/arm64 (support for M1 chipset) binaries and drop support for darwin/386.
Starting this release, we will publish darwin/arm64 (support for M1 chipset) binaries and drop support for darwin/386.
https://github.com/gruntwork-io/kubergrunt/pull/120
Update the aws-sdk-go version used to v1.38.14.
Update the aws-sdk-go version used to v1.38.14.
Special thanks to @sylr for their contribution!
This is an internal code cleanup release, where some functions were moved to a common library. There is no change in behavior to kubergrunt in this re
This is an internal code cleanup release, where some functions were moved to a common library. There is no change in behavior to kubergrunt in this release.
Nothing published for this version
eks sync-core-components (docs)
eks sync-core-components (docs)eks sync-core-components now supports k8s 1.19.
Special thanks to @FriedCircuits for their contribution!
eks cleanup-security-group (docs)
eks cleanup-security-group (docs)Fix bug where the cleanup routine did not work in accounts without the default VPC configured.
eks cleanup-security-group (docs)
eks cleanup-security-group (docs)We discovered a bug in the retry logic that handles ENIs detached before the request to detach can be sent, but there is no error returned.
eks cleanup-security-group (docs)
eks cleanup-security-group (docs)We discovered a bug in the logic that handles errors for the case when the ENI is detached before the request to detach can be sent.
eks cleanup-security-group (docs)
eks cleanup-security-group (docs)We increased the timeout for deleting resources leftover after destroying the EKS cluster.
eks cleanup-security-group (docs)
eks cleanup-security-group (docs)eks schedule-coredns ec2 (docs)eks schedule-coredns fargate (docs)We have added new commands to help with cleaning up security groups associated with an EKS cluster, and to toggle the CoreDNS service between scheduling on Fargate and EC2 worker types.
eks verify now uses the right kubergrunt executable, which is the currently running kubergrunt binary. Before, it was assuming that the currently runn
eks verifyeks verify now uses the right kubergrunt executable, which is the currently running kubergrunt binary. Before, it was assuming that the currently running kubergrunt binary was in the PATH environment variable. That is not always the case, and it's safer to use os.Executable() to get the absolute path of kubergrunt.
eks sync-core-components now supports Kubernetes version 1.18.
eks sync-core-componentseks sync-core-components now supports Kubernetes version 1.18.
The VPC CNI version that kubergrunt eks sync-core-components will upgrade to has been bumped to the latest version recommended by AWS (v1.7.5).
eks sync-core-componentsThe VPC CNI version that kubergrunt eks sync-core-components will upgrade to has been bumped to the latest version recommended by AWS (v1.7.5).
This introduces kubergrunt eks sync-core-components, which can be used to roll out updates to the core components of an EKS cluster after upgrading th
eks sync-core-components [NEW]This introduces kubergrunt eks sync-core-components, which can be used to roll out updates to the core components of an EKS cluster after upgrading the Kubernetes version. Refer to the AWS docs on the topic for more details.
The helm subcommand was removed in this release, now that Helm v2 is scheduled for end of life.
helm [REMOVED]The helm subcommand was removed in this release, now that Helm v2 is scheduled for end of life.
The compilation and build steps have also been switched to go modules instead of dep.
This is a backport fix to ensure that the helm 2 functionality works with the new location for the stable repository. See the helm announcement on the
This is a backport fix to ensure that the helm 2 functionality works with the new location for the stable repository. See the helm announcement on the new location for stable repository for more information.
NOTE: This release is marked as a pre-release to prevent it from bubbling as the latest release on the repository.
Starting this release, we will publish sha256 checksums with our binaries.
None
Starting this release, we will publish sha256 checksums with our binaries.
Special thanks to @DrFaust92 for their contribution!
All commands that take in kubernetes auth options.
All commands that take in kubernetes auth options.
This release introduces a new authentication option for kubernetes API calls to EKS, where it will create a temporary kubeconfig file using the AWS SDK.
This fixes a bug in the eks deploy command where it did not handle LoadBalancer Services that are internal.
eks deployThis fixes a bug in the eks deploy command where it did not handle LoadBalancer Services that are internal.
This fixes a nondeterministic failure in retrieving the thumbprint, where depending on timing, you are likely to fail retrieval of the OIDC thumbprint
eks oidcThis fixes a nondeterministic failure in retrieving the thumbprint, where depending on timing, you are likely to fail retrieval of the OIDC thumbprint when the EKS cluster is first launching.
This adds a new CLI arg --delete-local-data so that the rolling deployment can continue even if there are pods using emptyDir.
eks deployThis adds a new CLI arg --delete-local-data so that the rolling deployment can continue even if there are pods using emptyDir.
Special thanks to @adamrbennett for their contribution!
This introduces a new subcommand kubergrunt k8s kubectl, which is a thin wrapper around kubectl. This allows you to use the kubergrunt CLI args for au
k8s kubectl [NEW]This introduces a new subcommand kubergrunt k8s kubectl, which is a thin wrapper around kubectl. This allows you to use the kubergrunt CLI args for authenticating to the Kubernetes cluster. This is most useful when you want to pass in the server certificate authority data as a base64 encoded arg on the CLI, which you currently can not do with kubectl directly.
The helm grant command will now additionally grant permissions to get the Deployment resource that corresponds to the tiller deployment. This is neces
helm granthelm configureThe helm grant command will now additionally grant permissions to get the Deployment resource that corresponds to the tiller deployment. This is necessary to use the terraform helm provider.
The --helm-home option of the helm configure command can now be set using the environment variable, HELM_HOME.
The tls gen command now supports setting the DNS names in the Subject Alternative Name (SAN) of the certificate. You can configure this using the new
tls genThe tls gen command now supports setting the DNS names in the Subject Alternative Name (SAN) of the certificate. You can configure this using the new --tls-dns-name arg for the command.
Special thanks to @KyleMartin901 for their contribution!
#68 Update to AWS SDK 1.25.4 (latest version) so kubergrunt can be used in an EKS container that is assuming an IAM role
#68 Update to AWS SDK 1.25.4 (latest version) so kubergrunt can be used in an EKS container that is assuming an IAM role
The eks deploy command will now cordon all the old nodes before starting to drain them so that the evicted pods get scheduled on the new nodes in the
eks deployThe eks deploy command will now cordon all the old nodes before starting to drain them so that the evicted pods get scheduled on the new nodes in the cluster.
This release introduces a new command kubergrunt eks oidc-thumbprint which can be used to compute the root CA thumbprint for a given OpenID Connect Is
eks oidc-thumbprint [NEW]This release introduces a new command kubergrunt eks oidc-thumbprint which can be used to compute the root CA thumbprint for a given OpenID Connect Issuer. This thumbprint is necessary when setting up an OpenID Connect Provider for use with the IAM Roles for Service Accounts feature provided by EKS.
Any command that auths to Kubernetes API.
Any command that auths to Kubernetes API.
You can now specify the kubernetes config path to use using the environment variable KUBECONFIG.
Special thanks to @KyleMartin901 for their contribution!
Any command that requires TLS subject info.
Any command that requires TLS subject info.
The TLS subject info JSON previously only allowed one name for some of the fields (e.g org for organization), but it now allows using alternate names:
common_nameorg OR organizationorg_unit OR organizational_unitcity OR localitystate OR provincecountryThis release makes the labels used to tag the Kubernetes resources more robust so that they fit within the constraints of the label system. For exampl
helm granthelm revokeThis release makes the labels used to tag the Kubernetes resources more robust so that they fit within the constraints of the label system. For example, this will modify special characters before including them into as labels.
WARNING: This revoke command is incompatible with any grant commands that were run before this version. See the "Migration Notes" for details on how to revoke access to already granted entities.
The revoke command depends on labels that are set on the Role, RoleBinding, and Secret to be able to find them for deletion. The new labels are incompatible with the previous versions, preventing you from revoking entities that were granted prior to this version.
However, entities granted access on v0.4.0 can be revoked using the kubergrunt helm revoke command from v0.4.0.
This release introduces the helm revoke command, which will remove access to Tiller from the specified RBAC entities. This is done by removing:
helm granthelm revoke [NEW]This release introduces the helm revoke command, which will remove access to Tiller from the specified RBAC entities. This is done by removing:
RoleBinding that binds permissions to access the Kubernetes Secret containing the TLS key pair and the Tiller Pod.Role that grants permissions to access the Kubernetes Secret containing the TLS key pair and the Tiller Pod.Secret containing the client TLS certificate.To support the revoke action, this release updates the grant command to add labels to the Role, RoleBinding, and Secret that is generated.
WARNING: This revoke command is incompatible with any grant commands that were run before this version. See the "Migration Notes" for details on how to revoke access to already granted entities.
NOTE: This revoke command does not mark the TLS certificate as unusable. This means that if the entity is able to open a connection to the Tiller pod, they will be able to reuse the certificate. For a full revocation, you will need to reissue the certificates under a new CA that is installed in the Tiller pod.
The revoke command depends on labels that are set on the Role, RoleBinding, and Secret to be able to find them for deletion. Previous versions of kubergrunt did not set labels on these resources during the grant operation, making them incompatible with the implementation of revoke. If you wish to revoke access to entities that were granted access using a previous version of grant, follow these steps:
NAMESPACE/NAME, where NAMESPACE is the namespace where the ServiceAccount is defined, and NAME is the name of the ServiceAccount.ENTITY_ID_MD5.TILLER_NAMESPACE.kubectl:kubectl delete rolebinding "$ENTITY_ID_MD5-$ENTITY_ID_MD5-$TILLER_NAMESPACE-tiller-access-binding" -n "$TILLER_NAMESPACE"
kubectl delete role "$ENTITY_ID_MD5-$TILLER_NAMESPACE-tiller-access" -n "$TILLER_NAMESPACE"
kubectl delete secret "tiller-client-$ENTITY_ID_MD5-certs" -n "$TILLER_NAMESPACE"
Special thanks to @bwhaley for their contribution!
Any commands that accept TLS configurations
helm configureThis release updates kubergrunt helm configure with a new option --as-tf-data, which enables you to call it in an external data source. Passing this flag will cause the command to output the configured helm home directory in the output json on stdout at the end of the command.
Additionally, kubergrunt helm configure now supports a new option you can set for --helm-home (E.g --helm-home __TMP__) to inform kubergrunt that you intend to use a tmp directory for the configured helm home directory. Passing this option in will cause the command to generate a new directory in the tmp folder for the platform to use as the helm home.
The above two features, when used in combination, allows you to dynamically configure the helm provider on the host machine in Terraform.
Finally, this release also updates the TLS subject json parsing for the CLI such that it can accept equivalent arg names in the terraform TLS subject block: https://www.terraform.io/docs/providers/tls/r/cert_request.html#common_name
This release updates the tls gen command to use the new way of authenticating to Kubernetes (specifically passing in server and token info directly) a
tls genhelm wait-for-tiller [NEW]This release updates the tls gen command to use the new way of authenticating to Kubernetes (specifically passing in server and token info directly) and using JSON to configure the TLS subject.
This release also introduces a new command helm wait-for-tiller which can be used to wait for a tiller deployment to roll out Pods, and have at least one Pod that can be pinged. This enables chaining calls to helm after helm is deployed when using a different helm deployment process that doesn't rely on the helm client (e.g creating deployment resources manually).
This release introduces the k8s wait-for-ingress sub command which can be used to wait until an Ingress resource has an endpoint associated with it.
k8s wait-for-ingress [NEW]This release introduces the k8s wait-for-ingress sub command which can be used to wait until an Ingress resource has an endpoint associated with it.
All commands that setup TLS certificates (e.g helm deploy and helm grant) can now take in the TLS subject information as a json.
All commands that setup TLS certificates (e.g helm deploy and helm grant) can now take in the TLS subject information as a json.
All commands that need to authenticate to Kubernetes (e.g eks deploy, helm deploy, etc) now take in direct authentication parameters as an alternative
All commands that need to authenticate to Kubernetes (e.g eks deploy, helm deploy, etc) now take in direct authentication parameters as an alternative means to auth. You can now pass in the authentication parameters --kubectl-server-endpoint, --kubectl-certificate-authority and --kubectl-token to the command to setup authentication to the Kubernetes cluster, as opposed to setting up the config.
The eks token command now accepts a new parameter --as-tf-data, which will encode the token output in a format that can be used as an external data so
eks tokenThe eks token command now accepts a new parameter --as-tf-data, which will encode the token output in a format that can be used as an external data source in terraform. This allows you to configure the kubernetes and helm providers without configuring a kubectl context.
This release introduces the tls gen sub command which can be used to generate TLS certificate key pairs that are managed using Kubernetes Secrets.
tls gen [NEW]This release introduces the tls gen sub command which can be used to generate TLS certificate key pairs that are managed using Kubernetes Secrets.
This release fixes the following bugs:
helm deployThis release fixes the following bugs:
helm deploy was not able to successfully authenticate against a GKE cluster on Google Cloud Platform.Additional improvements:
Gopkg.lock file.This release introduces the following new feature:
helm deployhelm configureThis release introduces the following new feature:
helm deploy, using the --tiller-image and --tiller-version flags.This release fixes the following bugs:
helm deploy had a bug where the client was configured after Tiller was confirmed to be deployed. However, the Tiller deployment check requires connecting to Tiller, leading to a chicken and egg problem. This fixes that by delaying the polling step until after the client has been granted access and configured.helm configure did not setup the helm home directory with the initial set of repository, leading the operator to run the repo update command immediately after configuring. This fixes that by installing the stable repo as part of configure.helm deploy required finding the executable kubergrunt in the PATH, exactly as is. This removes that need.Additional improvements:
helm deploy now uses the helm go library instead of calling out to the helm client.helm deploy had a bug where the client certificates were generated using the same parameters as the server certificates. Fixing this requires new requ
helm deploy [BREAKING CHANGE]This release fixes two bugs:
helm deploy had a bug where the client certificates were generated using the same parameters as the server certificates. Fixing this requires new required parameters to the command: --client-tls-common-name and --client-tls-org.helm deploy had a bug where it ignored the --helm-home directory when deploying Tiller. This prevented a custom home directory from being initialized.This release updates the helm deploy command to now require an RBAC entity to be passed in (one of --rbac-user, --rbac-group, or --rbac-service-accoun
helm deploy [BREAKING CHANGE]This release updates the helm deploy command to now require an RBAC entity to be passed in (one of --rbac-user, --rbac-group, or --rbac-service-account), which will be used to configure the local helm client.
This ensures that you can interact with helm immediately after a deploy, without the need to grant and configure.
This release introduces a suite of subcommands that can be used to deploy helm with all the official security best practices considered. Take a look a
helm deploy [NEW]helm undeploy [NEW]helm configure [NEW]helm grant [NEW]This release introduces a suite of subcommands that can be used to deploy helm with all the official security best practices considered. Take a look at the command help text for more information.
This is a compatible release of kubergrunt with `package-k8s` v0.1.4.
eks configureeks tokeneks deployThis is a compatible release of kubergrunt with package-k8s v0.1.4.
Nothing published for this version
Nothing published for this version
One column per quarter.