Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

kops 1.29.0 #171874

Merged
merged 2 commits into from
May 16, 2024
Merged

kops 1.29.0 #171874

merged 2 commits into from
May 16, 2024

Conversation

BrewTestBot
Copy link
Member

Created by brew bump

Created with brew bump-formula-pr.

release notes 
# Significant changes

Deferred deletion / pruning phase


Some infrastructure changes are potentially disruptive to the continued

operation of the cluster.  For the most disruptive operations, particularly

those that break rolling-update of the cluster, we have started to use deferred

deletion to minimize the impact.  For example, on AWS we create a second NLB

during the kops update phase when we cannot change the NLB directly.

kops update will report that a --prune is needed.  To minimize disruption,

we recommend you perform this after a rolling-update, for example:


kops update $MYCLUSTER --yes --admin
kops rolling-update $MYCLUSTER --yes
kops update $MYCLUSTER --yes --admin --prune # NEW!



Deferred deletion is currently used to safely introduce security groups for NLBs on AWS,

and to move to an internal load balancer for kops-controller on GCP.


Initial OpenTelemetry Support


We are starting to add (experimental) support for OpenTelemetry,

in particular Tracing support.  Setting OTEL_EXPORTER_OTLP_TRACES_FILE

will write a trace file which can then be read by the traceserver program.

More information and options are described in docs/opentelemetry.md.

The tracing data is not expected to be particularly useful for end-users in

this release; the (non-standard) recording approach is instead intended to

work well with our Prow end-to-end testing system so that developers can

optimize kOps.


Please note: this is not telemetry in the "phone-home" sense.

The kOps project does not collect data from your machine.  As an

open-source project we do not even want to collect any of your data.

Currently the only OpenTelemetry backend supported is writing to a

filesystem (and it is opt-in).  In future you will be able to configure

other OpenTelemetry backends, but this data will only be sent if

you enable OpenTelemetry, and only sent to where you configure.


AWS


    

  • 

    Network Load Balancers in front of the Kubernetes API and bastion hosts now
    
have a security group attached. These security groups are used for security group rules
    
allowing incoming traffic to the NLBs as well as traffic between the NLBs and their target
    
instances.
    

    • 

  • 

    Posts event data to URL upon instance interruption action in aws-node-termination-handler with WEBHOOK_URL.
    

    • 



GCP


    

  • 

    As of Kubernetes version 1.29, credentials for private GCR/AR repositories will be handled by the out-of-tree credential provider. This is an additional binary that each instance downloads from the assets repository.
    

    • 

  • 

    Two additional StorageClasses are created on GCP clusters. These are called balanced-csi and ssd-csi and utilize the GCP Balanced and SSD Persistent Disk volume types respectively.
    

    • 

  • 

    Breaking Change - the default StorageClass has been changed from standard-csi to balanced-csi.
    

    • 

  • 

    We now use a private load-balancer for in-cluster traffic on GCP, which allows us
    
to use network tags to restrict access only to the cluster nodes.
    

    • 



Breaking changes


Other breaking changes


    

  • 

    kops toolbox dump limits the number of nodes dumped to 500 by default. Use --max-nodes to override.
    

    • 

  • 

    Support for Kubernetes version 1.23 has been removed.
    

    • 



Known Issues



Deprecations


    

  • 

    Support for Kubernetes version 1.24 is deprecated and will be removed in kOps 1.30.
    

    • 

  • 

    Support for Kubernetes version 1.25 is deprecated and will be removed in kOps 1.31.
    

    • 

  • 

    Support for AWS Classic Load Balancer for API is deprecated and should not be used for newly created clusters.
    

    • 

  • 

    All unmanaged addons (in addons/) are deprecated in favor of managed addons, including the metrics server addon and the autoscaler addon.
    

    • 



What's Changed



New Contributors



Full Changelog since 1.28.0: kubernetes/kops@v1.28.0...v1.29.0

@github-actions github-actions bot added go Go use is a significant feature of the PR or issue bump-formula-pr PR was created using `brew bump-formula-pr` labels May 16, 2024
@github-actions GitHub Actions
Copy link
Contributor

🤖 An automated task has requested bottles to be published to this PR.

@github-actions github-actions bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label May 16, 2024
@BrewTestBot BrewTestBot added this pull request to the merge queue May 16, 2024
Merged via the queue into master with commit e4ca7eb May 16, 2024
14 checks passed
@BrewTestBot BrewTestBot deleted the bump-kops-1.29.0 branch May 16, 2024 13:21
@github-actions github-actions bot added the outdated PR was locked due to age label Jun 21, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

@krehel krehel krehel approved these changes

Assignees
No one assigned
Labels
bump-formula-pr PR was created using `brew bump-formula-pr` CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. go Go use is a significant feature of the PR or issue outdated PR was locked due to age
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@BrewTestBot @krehel