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

feat(installer): transfor influxdb sts to depl #1959

Merged

Conversation

leoryu
Copy link
Contributor

@leoryu leoryu commented May 24, 2022

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind api-change
/kind bug
/kind cleanup
/kind deprecation
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@leoryu leoryu requested a review from choujimmy as a code owner May 24, 2022 03:09
@leoryu leoryu merged commit 84ad480 into tkestack:industry-cloud-1.9 May 24, 2022
@leoryu leoryu deleted the feat/trans_stafulset_deployment branch May 24, 2022 03:15
leoryu pushed a commit that referenced this pull request Apr 19, 2023
* fix(installer): add insecure-registry (#2258)

* refactor(logagent): update log file port (#1872)

* feat(installer): disabel import charts (#1879)

* feat(gateway): use node port instead (#1890)

* fix(installer): change install ingress step

* fix(installer): correct gateway manifest (#1902)

* fix(installer): stop uninstall gateway chart (#1903)

* fix(installer): remove servicename in deployment (#1960)

* feat(installer): transfor influxdb sts to depl (#1959)

* fix(installer): fix check influxdb func

* fix(installer): correct go lint
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.

None yet

1 participant