Provide high quality multiarch docker images and k8s support

Hey Tom, it looks like that link is also dead and the repo may have been moved. Do you have a link to the new location? Thanks a ton for all your effort, you’re truly doing great work.

The PR is here: [Part 5] - Provide high quality multiarch docker image and k8s support by tdiesler · Pull Request #2608 · input-output-hk/cardano-node · GitHub

Hi! What docker image do you recomend using with k8 and cardano? The official, or the image from nessus?

Currently, you would still want to use nessus. For upstream progress you can monitor PR #2608

1 Like

@tomdx , there is some grafana dashboard around there for nessus docker image?

Not as part of the nessusio project. In case you’d like to add it, you are welcome to create an associated issue + PR.

1 Like

All right. I’ll check some examples of dashboards and I’ll do it. I saw that not all the docker images provide the same metrics with node exporter.

Hello, in this file, that is suggested in the tutorial, you use two services to connect the realy node through a tcp connection to the outside world: relay-np and relay-clip. Do I need to define those services for a new relay node?

In this README you are using the stateful sets. I’m also using stateful set, so in this approach, this is the service you are using to connect relay nodes to the external world:

apiVersion: v1
kind: Service
  namespace: cardano
  name: relay-headless
  type: ClusterIP
  clusterIP: None
  sessionAffinity: None
  - port: 3001 # Port 3001 must be reachable for external ingress
    protocol: TCP
    targetPort: 3001
    app: cardano
    pod: relay

So the endpoints would be the pods which its name is relay. But why the clusterIP is none? And what is a service of type clusterIP?

And what means
# Port 3001 must be reachable for external ingress ?
Do I need to configure a firewall rule?

1 Like