Service Options and Network Options configuration

[varun6121990]

Hi Team,

We are just in the implementation phase of bringing in Cryostat in to our Kube cluster. We are using AWS EKS.

Service options

As per the documentation of cryostat-operator, we are unable to expose core Cryostat application, Grafana, and cryostat-reports as service. The schema definition of cryostats.operator.cryostat.io does not have Service options itself. Attached the schema file for your reference. Please let us know how to expose these 3 as services.
schema.txt

Network Options

We are trying to use istio-ingress in ingress specification. But we are not able to get the pods in our namespace after applying the below yaml, only we could able to see these components coming as load balancer.

---
apiVersion: operator.cryostat.io/v1beta1
kind: Cryostat
metadata:
  name: cryostat-sample
spec:
  trustedCertSecrets: []
  enableCertManager: false
  minimal: false
  networkOptions:
    coreConfig:
      annotations:
        kubernetes.io/ingress.class: istio
        name: ingress
      ingressSpec:
          ingressClassName: kubernetes.io/ingress.class
          rules:
          -     host: testing.cryostat
                http:
                    paths:
                    -     backend:
                              service:
                                  name: cryostat-sample
                                  port:
                                      number: 443
                          path: /
                          pathType: Prefix

Output: kubectl get svc -n dev
Name Type Port
cryostat-sample LoadBalancer 8181:30629/TCP,9091:30040/TCP 26m
cryostat-sample-grafana LoadBalancer 3000:32348/TCP 26m

Please help us on the above issues.

[ebaron]

Hi there. It appears that you're using our latest released version: 2.0.0. The service configuration is a new feature that will appear in our next release.

Troubleshooting networking issues in Kubernetes can be difficult, is it possible to disable Istio for this namespace in order to isolate the problem?

You mentioned that no pods are being created. Can you attach the logs for the operator pod? Its name will begin with cryostat-operator-controller-manager.

[varun6121990]

@ebaron Thanks for your reply!!! When we could expect the next release with service options ??

[ebaron]

We expect that release to happen within the next 1-2 months.

[tthvo]

Hey @ebaron this is done in 2.1.0?

[ebaron]

Hey @ebaron this is done in 2.1.0?

The options to customize services were done for that release. There is still the possibility of using services directly without routes or ingresses, but let's track that with #403.