We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Dear Devs,
during setup an environment, we got few time the issue, that in the network provider config hosts are missing or wrong annotated.
is it possible to extend this mechanism by an includeNodes and add by-label feature?
this is the manifest from the docu
apiVersion: kubeovn.io/v1 kind: ProviderNetwork metadata: name: net1 spec: defaultInterface: eth1 customInterfaces: - interface: eth2 nodes: - node1 excludeNodes: - node2
some examples for an implementation:
apiVersion: kubeovn.io/v1 kind: ProviderNetwork metadata: name: net1 spec: defaultInterface: eth1 customInterfaces: - interface: eth2 nodes: - node1 includeNodes: - labels: node-role.kubernetes.io/worker - nodes: - node2
apiVersion: kubeovn.io/v1 kind: ProviderNetwork metadata: name: net1 spec: defaultInterface: eth1 customInterfaces: - interface: eth2 nodes: - node1 excludeNodes: - labels: node-role.kubernetes.io/worker
Me, and customers how be able to change the node roles dynamically.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
Dear Devs,
during setup an environment, we got few time the issue, that in the network provider config hosts are missing or wrong annotated.
is it possible to extend this mechanism by an includeNodes and add by-label feature?
this is the manifest from the docu
some examples for an implementation:
Who will benefit from this feature?
Me, and customers how be able to change the node roles dynamically.
Anything else?
No response
The text was updated successfully, but these errors were encountered: