Skip to content

fix: update cluster name in deploy_preview script and adjust kubeconf…#40981

Merged
pratapaprasanna merged 1 commit intoreleasefrom
chore/migrate/dp/uatx
Jun 25, 2025
Merged

fix: update cluster name in deploy_preview script and adjust kubeconf…#40981
pratapaprasanna merged 1 commit intoreleasefrom
chore/migrate/dp/uatx

Conversation

@pratapaprasanna
Copy link
Contributor

@pratapaprasanna pratapaprasanna commented Jun 19, 2025

…ig command

📝 Summary

This commit updates the cluster name in the deploy_preview.sh script from uat-cluster to uatx-cluster and modifies the aws eks update-kubeconfig command to remove the profile option, ensuring compatibility with the current AWS configuration.

🎨 Changes Made

  • Cluster Name Update: Changed export cluster_name=uat-cluster to export cluster_name=uatx-cluster.
  • Kubeconfig Command Adjustment: Removed the --profile eksci option from the aws eks update-kubeconfig command for streamlined execution.

No user-facing changes were made, and the script remains functional for deployment tasks.

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • Chores
    • Updated the AWS EKS cluster name used in deployment processes.
    • Modified deployment script to use default AWS credentials for cluster configuration.

…ig command

### 📝 Summary
This commit updates the cluster name in the `deploy_preview.sh` script from `uat-cluster` to `uatx-cluster` and modifies the `aws eks update-kubeconfig` command to remove the profile option, ensuring compatibility with the current AWS configuration.

### 🎨 Changes Made
- **Cluster Name Update**: Changed `export cluster_name=uat-cluster` to `export cluster_name=uatx-cluster`.
- **Kubeconfig Command Adjustment**: Removed the `--profile eksci` option from the `aws eks update-kubeconfig` command for streamlined execution.

No user-facing changes were made, and the script remains functional for deployment tasks.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 19, 2025

Walkthrough

The deployment script was updated to use a new AWS EKS cluster name and now configures kubeconfig without specifying an AWS profile, relying on default credentials or environment variables. No other logic or functional aspects of the script were changed.

Changes

File(s) Change Summary
scripts/deploy_preview.sh Changed EKS cluster name from uat-cluster to uatx-cluster; updated kubeconfig command to remove --profile eksci and rely on default credentials.

Poem

A cluster once named UAT,
Now wears an X with pride.
No profile to specify,
Default creds will now guide.
Deployments march on,
As the preview script is donned!
🚀

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the Bug Something isn't working label Jun 19, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
scripts/deploy_preview.sh (1)

51-53: Review kubeconfig command changes

  • Removing --profile eksci is valid if AWS creds are managed via environment or default profile.
  • Consider deleting the commented-out legacy command to keep the script tidy.
    Please test this in both CI and your local environment to confirm the correct credentials are picked up.
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ad36f76 and e844880.

📒 Files selected for processing (1)
  • scripts/deploy_preview.sh (2 hunks)
🔇 Additional comments (1)
scripts/deploy_preview.sh (1)

14-14: Cluster name updated – verify resource existence
Ensure that the new cluster uatx-cluster is provisioned and accessible in your AWS account to prevent silent failures during the preview deployment.

@pratapaprasanna pratapaprasanna merged commit 0c0648e into release Jun 25, 2025
17 checks passed
@pratapaprasanna pratapaprasanna deleted the chore/migrate/dp/uatx branch June 25, 2025 11:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant