Skip to content

4.5.0 - May 18, 2023
Compare
Choose a tag to compare
@jarpat jarpat released this 18 May 15:02
· 46 commits to main since this release
4.5.0
3d204d5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release Notes

gke-gcloud-auth-plugin dependency for K8s v1.26

In this release the provider based kubernetes configuration file format, created by setting create_static_kubeconfig=false, will change to support the use of the gke-gcloud-auth-plugin. The gke-gcloud-auth-plugin binary is required to access any GKE clusters when using kubectl 1.26+ with a "provider based" kubernetes configuration file. The "service account and cluster role binding" kubernetes configuration file variant remains the same and still does not require either gcloud or the gke-gcloud-auth-plugin binary to communicate with the cluster.

In our included Dockerfile we included steps to ensure that the plugin is installed as well as enabled. If you are opting not to this project via a Docker container produced with our Dockerfile, you will need to take steps to install both gcloud and gke-gcloud-auth-plugin on your machine. Google has provided step-by-step instructions in a blog post to aid users with this transition. See Google's Authentication Blog post.

For additional information about kubernetes configuration files, see our Kubernetes Configuration File Generation documentation

Also, to support using this updated provider based kubernetes configuration file in GKE to perform SAS Viya platform deployments, the viya4-deployment project has updated to handle this type kubernetes configuration file in release 6.6.0. See the Kubernetes Configuration File Types documentation from the viya4-deployment project.

ENHANCEMENTS:

  • #169: feat: (IAC-695) Add Support for K8s 1.26
Assets 2
Loading