Charts[GKE-BUG] Apply nodeSelector to all pods in the chart including proxies

[leninmehedy]

Currently network-node pods are scheduled based on the following settings:

  nodeSelectors:
    fullstack-scheduling.io/os: linux
    fullstack-scheduling.io/role: network
  tolerations:
    - key: "fullstack-scheduling.io/os"
      operator: "Equal"
      value: "linux"
      effect: "NoSchedule"
    - key: "fullstack-scheduling.io/role"
      operator: "Equal"
      value: "network"
      effect: "NoSchedule"

We need to ensure these settings are applied for all pods in the chart including proxies.

[leninmehedy]

It is tricky to pass nodeSelector and tolerations to dependent charts. After updating the values file, I was expecting all pods to be in pending state (since they should not have any appropriate node), however some of the pods from dependent charts are still running...

Besides, it makes our values.yaml file too much verbose since we need to duplicate and maintain nodeSelector and toleration settings for all dependent charts (see PR: #384).

[steven-sheehy]

Can just disable rest-monitor via rest.monitor.enabled=false. It's not necessary for FST. Should also probably disable other monitor, rosetta, and graphql. We've disabled the latter two by default in latest RC.

[steven-sheehy]

And with some config we can get rid of redis and pgpool, if we want to further reduce the number of containers.

[leninmehedy]

Thanks @steven-sheehy

[leninmehedy]

And with some config we can get rid of redis and pgpool, if we want to further reduce the number of containers.

@steven-sheehy Could you point me to the config? If redis and pgpool are not required, I can disable those by default in our chart.

Here is a list of containers after disabling some of the mirror-node containers as you suggested. Does that look ok?

[steven-sheehy]

Could you point me to the config? If redis and pgpool are not required, I can disable those by default in our chart.

Sure, you can borrow from our GCP Marketplace values.yaml. Specifically, copy the
grpc.config, importer.config except cloudProvider, and postgresql.pgpool.replicaCount=0.

Here is a list of containers after disabling some of the mirror-node containers as you suggested. Does that look ok?

The list of containers is okay, but rest and importer pods are not ready. Do you know why?

[leninmehedy]

The list of containers is okay, but rest and importer pods are not ready. Do you know why?

It just takes a bit longer to be ready.

[swirlds-automation]

🎉 This issue has been resolved in version 0.12.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀