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

doc: Update devtron-reference charts with pdb #3719

Merged
merged 4 commits into from
Aug 21, 2023

Conversation

Abhinav-26
Copy link
Member

Description

Updated Devtron reference helm charts with podDisruptionBudget to show in README as well in Devtron UI

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

Users using Rollout chart - 4-16-0, 4-17-0, 4-18-0 will now be able to see the podDisruptionBudget field in the Deployment template.

@Abhinav-26 Abhinav-26 requested a review from prakarsh-dt August 2, 2023 08:38
prakarsh-dt
prakarsh-dt previously approved these changes Aug 18, 2023
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@prakarsh-dt prakarsh-dt changed the title docs: Update devtron-reference charts with pdb doc: Update devtron-reference charts with pdb Aug 21, 2023
@prakarsh-dt prakarsh-dt merged commit b94c5f0 into devtron-labs:main Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants