This repository has been archived by the owner on May 31, 2024. It is now read-only.
Fix flyteadmin port in flytectl config init
#400
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL;DR
Fix the flyteadmin port by
flytectl config init
to match the one required by demo clusterType
Are all requirements met?
Complete description
The flyteadmin port used in the demo cluster is 30080, so users who have rely on
flytectl config init
to generate a valid config file should be left with a config file that reflects that.Tracking Issue
flyteorg/flyte#3461
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/