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.

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

Create Blog Post for EKS v3 release #13040

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

flostadler
Copy link
Contributor

Proposed changes

This adds the blog post for the EKS v3 release. It's currently set to draft and will be set to public when released. The links to the migration guide will need to be updated once they're uploaded to the registry.

Related issues (optional)

relates to https://github.com/pulumi/home/issues/3558

3. Update your code to handle new output types for certain properties.
4. Review and update your use of default security groups, which can now be disabled.

For a detailed migration guide, please refer to our [EKS v3 Migration Documentation](https://github.com/pulumi/pulumi-eks/blob/release-3.x.x/docs/eks-v3-migration.md).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The migration guide will be updated to point to the registry once it's published.

@pulumi-bot
Copy link
Collaborator

@t0yv0
Copy link
Member

t0yv0 commented Oct 4, 2024

Did you find a link to it in preview? http://www-testing-pulumi-docs-origin-pr-13040-c3bbdb6a.s3-website.us-west-2.amazonaws.com/blog/ not showing it seems


Pulumi EKS v3 introduces better support for the Kubernetes Cluster Autoscaler. A new `ignoreScalingChanges` parameter for node groups allows Pulumi to ignore external scaling changes, facilitating seamless integration with dynamic scaling solutions.

### EKS Security Groups for Pods and Network Policies
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be pretty cool to link to minimal examples if possible I think.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah good idea, I started creating some for those new features!

@flostadler
Copy link
Contributor Author

Did you find a link to it in preview? http://www-testing-pulumi-docs-origin-pr-13040-c3bbdb6a.s3-website.us-west-2.amazonaws.com/blog/ not showing it seems

Ah well, that's interesting. Setting the blog post to draft also hid it in the preview build, but locally it's showing up.
I'll set draft to false for now. In that case we'll have to hold off with merging this until Friday

The latest major release of the Pulumi EKS Provider is available now!

AWS recently announced the deprecation of two features used by default in Pulumi EKS: the aws-auth ConfigMap and the AL2 operating system. Pulumi EKS v3 addresses these deprecations, enhances the maintainability of the provider, and aligns it with EKS best practices.
This release delivers significant improvements in flexibility and security, introducing new features to enhance your Kubernetes experience on AWS.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe lead with the positive impact for users, rather than deprecations that we had to deal with which sounds more like just maintenance?


### Access Entries for IAM Integration

AWS has introduced Access Entries as a new method for granting IAM principals access to Kubernetes resources. This approach relies solely on AWS resources for managing Kubernetes auth, replacing the deprecated `aws-auth` ConfigMap. You can now leverage Access Entries by setting the `authenticationMode` to `API` in your cluster configuration.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

link "Access Entries" to AWS docs?

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

Copy link
Contributor

@thomas11 thomas11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants