Skip to content

Conversation

@prakarsh-dt
Copy link
Collaborator

Description

When using ingress in legacy format with the latest chart versions, it inserts the example.com values in the created ingress and gives pathType expected error.

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test case A
  • Test case B

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR require 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

@prakarsh-dt
Copy link
Collaborator Author

Needs to be replicated and tested for all chart versions 3.11.0 onwards

@prakarsh-dt prakarsh-dt changed the title Fix ingress new and legacy compatibility issues WIP: Fix ingress new and legacy compatibility issues Mar 12, 2022
@gunish-dt gunish-dt mentioned this pull request Apr 20, 2022
13 tasks
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.

3 participants