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

make master node only for DISKLESS as TieBreaker #653

Open
yeshl opened this issue Apr 26, 2024 · 3 comments
Open

make master node only for DISKLESS as TieBreaker #653

yeshl opened this issue Apr 26, 2024 · 3 comments

Comments

@yeshl
Copy link

yeshl commented Apr 26, 2024

i want make master node only for DISKLESS as TieBreaker , whether I configure spec.nodeSelector/spec.nodeAffinity in linstorcluster or LinstorSatelliteConfiguration,it is not working!lost master satellite!

WARNING:
Description:
    No active connection to satellite 'master0.k8s'
Details:
    The controller is trying to (re-) establish a connection to the satellite. The controller stored the changes and as soon the satellite is connected, it will receive this update.
@WanzenBug
Copy link
Member

Is the satellite actually running on master0.k8s? Is there any kind of firewall or similar that would prevent the connection?

@yeshl
Copy link
Author

yeshl commented Apr 27, 2024

I found the solution:

1. piraeus-operator and linstorcluster
       tolerations:
        - key: node-role.kubernetes.io/master
          operator: Exists
          effect: NoSchedule
        - key: node-role.kubernetes.io/control-plane
          operator: Exists
          effect: NoSchedule

2. LinstorSatelliteConfiguration
  nodeSelector:
    kubernetes.io/os: linux
    zwsx.io/storage: "yes"
  patches:
    - target:
        kind: Pod
        name: satellite
      patch: |
        apiVersion: v1
        kind: Pod
        metadata:
          name: satellite
        spec:
          tolerations:
            - key: node-role.kubernetes.io/master
              operator: Exists
              effect: NoSchedule
            - key: node-role.kubernetes.io/control-plane
              operator: Exists
              effect: NoSchedule    

@lucacalcaterra
Copy link

lucacalcaterra commented May 28, 2024

I found the solution:

1. piraeus-operator and linstorcluster
       tolerations:
        - key: node-role.kubernetes.io/master
          operator: Exists
          effect: NoSchedule
        - key: node-role.kubernetes.io/control-plane
          operator: Exists
          effect: NoSchedule

2. LinstorSatelliteConfiguration
  nodeSelector:
    kubernetes.io/os: linux
    zwsx.io/storage: "yes"
  patches:
    - target:
        kind: Pod
        name: satellite
      patch: |
        apiVersion: v1
        kind: Pod
        metadata:
          name: satellite
        spec:
          tolerations:
            - key: node-role.kubernetes.io/master
              operator: Exists
              effect: NoSchedule
            - key: node-role.kubernetes.io/control-plane
              operator: Exists
              effect: NoSchedule    

I need too :-) Can you specify ? piraeus-operator, where ? Can you share your config for this ? Which version do you use ? Thanks !

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

No branches or pull requests

3 participants