Skip to content

fix: default connect.serviceType to ClusterIP #217

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

Merged
merged 1 commit into from
Jun 23, 2025

Conversation

bo0tzz
Copy link
Contributor

@bo0tzz bo0tzz commented Dec 12, 2024

Fixes #194

@onedr0p
Copy link

onedr0p commented May 21, 2025

@edif2008 do you have a minute to review this? Thanks!

@volodymyrZotov volodymyrZotov merged commit f1a3ed0 into 1Password:main Jun 23, 2025
1 check passed
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.

Connect exposed as NodePort service by default
3 participants