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: specify the host IP as the k8s internal IP #5196

Merged
merged 1 commit into from
Nov 13, 2024

Conversation

ghostloda
Copy link
Collaborator

@ghostloda ghostloda commented Nov 8, 2024

使用部署时指定的主机地址作为集群internal IP,可以避免在多网卡的环境中,自动识别到错误的网卡。
#2465
#2594

@sealos-ci-robot
Copy link
Member

🤖 Generated by lychee action

Summary

Status Count
🔍 Total 2165
✅ Successful 492
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 1670
❓ Unknown 0
🚫 Errors 1

Errors per input

Errors in docs/blog/zh-Hans/2024/how-to-deploy-and-configure-meilisearch-using-docker/index.md

Full action output

Full Github Actions output

@ghostloda ghostloda changed the title feat: specify the host IP as the node internal IP feat: specify the host IP as the k8s internal IP Nov 8, 2024
@ghostloda ghostloda requested a review from cuisongliu November 13, 2024 01:45
@cuisongliu cuisongliu merged commit 76c93a6 into labring:main Nov 13, 2024
88 of 91 checks passed
@ming2281
Copy link

@ghostloda @cuisongliu
Hi,这个特性要如何配置使用?
发现sealos工具并没有入口可以使用

我的主机环境是

  1. 网卡1: DHCP IP ,会变化, 带默认路由
  2. 网卡2: 静态IP

我现在试了很多种方法,发现无论怎么做,都会使用网卡1的IP

@sealos-ci-robot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


@ghostloda @cuisongliu
Hi, how to configure and use this feature?
Found that the sealos tool has no entrance to use

My hosting environment is

  1. Network card 1: DHCP IP, will change, with default route
  2. Network card 2: Static IP

I have tried many methods now and found that no matter what I do, the IP of network card 1 will be used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants