Hi Nitin,
On 2021-11-18 2:13 p.m., Nitin Ghuge wrote:
> Hi All,
>
> Installed Cryostat Operator and also deployed Cryostat in my
> customized namespace of Azure Kubernetes environment. But I am not able
> to access cryostat web dashboard. So can't generate JFR for my application
>
> 1. I tried to get the url using below command but it failed.
>
> kubectl --kubeconfig=/c/Users/abc/.kube/kubeconfig get cryostat
> -o jsonpath='{$.items[0].status.applicationUrl}'
>
> error: error executing jsonpath
> "{$.items[0].status.applicationUrl}": Error executing template: array
> index out of bounds: index 0, length 0. Printing more information for
> debugging the template:
> template was:
> {$.items[0].status.applicationUrl}
> object given to jsonpath engine was:
> map[string]interface {}{"apiVersion":"v1",
> "items":[]interface {}{}, "kind":"List", "metadata":map[string]interface
> {}{"resourceVersion":"", "selfLink":""}}
It seems like something is preventing Cryostat from being deployed
properly. Could you check if there are any Events listed when you run:
> $ kubectl describe cryostat <name of cryostat instance>
>
> 2. I think there is alternative of event template for jfr
> generation. Can you please provide me any such event template file?
Once Cryostat is up and running, you can follow this guide to download,
edit and upload customized event templates:
https://cryostat.io/guides/#download-edit-and-upload-a-customized-event-template.
Alternatively, you can find the built-in JFR event templates that are
shipped with OpenJDK under: $JAVA_HOME/lib/jfr. The file extension is
.jfc, but they are XML files.
Thanks,
Elliott
>
> Regards,
> Nitin
>
>
> On Monday, November 15, 2021 at 10:01:50 PM UTC+5:30 Elliott Baron wrote:
>
> Hi Nitin,
>
> This is something you can do with Kustomize. Create a
> kustomization.yaml
> file in the directory of your choice like this one:
>
> > $ cat kustomization.yaml
> > bases:
> > -
>
github.com/cryostatio/cryostat-operator/config/default?ref=v2.0.0
> <
http://github.com/cryostatio/cryostat-operator/config/default?ref=v2.0.0>
>
> >
> > namespace: abcd
>
> This will override the namespace of any operator resources with "abcd".
> To deploy, from the same directory run:
>
> > kubectl apply -k .
>
> This tells kubectl to apply resources using the kustomization.yaml file
> in your current directory.
>
> Thanks,
> Elliott
>
> On 2021-11-12 1:27 p.m., Nitin Ghuge wrote:
> > Hi,
> >
> > I am working on JFR generation of application deployed on Azure
> > Kubernetes cluster environment.
> > I am trying to setup Cryostat operator using below command. I am
> > trying to setup it on my own namespace "abcd" because my existing
> > application is well established within this namespace.
> >
> > kubectl --kubeconfig=/c/Users/.kube/kubeconfig -n abcd apply
> > --namespace=abcd -k
> >
> '
github.com/cryostatio/cryostat-operator//config/default?ref=v2.0.0
> <
http://github.com/cryostatio/cryostat-operator//config/default?ref=v2.0.0>'
> <
http://customresourcedefinition.apiextensions.k8s.io/cryostats.operator.cryostat.io>
>
> > configured
> >
>
customresourcedefinition.apiextensions.k8s.io/flightrecorders.operator.cryostat.io
> <
http://customresourcedefinition.apiextensions.k8s.io/flightrecorders.operator.cryostat.io>
>
> > configured
> >
>
customresourcedefinition.apiextensions.k8s.io/recordings.operator.cryostat.io
> <
http://customresourcedefinition.apiextensions.k8s.io/recordings.operator.cryostat.io>
>
> > configured
> >
clusterrole.rbac.authorization.k8s.io/cryostat-operator-cryostat
> <
http://clusterrole.rbac.authorization.k8s.io/cryostat-operator-cryostat>
> configured
> >
clusterrole.rbac.authorization.k8s.io/cryostat-operator-role
> <
http://clusterrole.rbac.authorization.k8s.io/cryostat-operator-role> configured
>
> >
>
clusterrolebinding.rbac.authorization.k8s.io/cryostat-operator-cluster-role-binding
> <
http://clusterrolebinding.rbac.authorization.k8s.io/cryostat-operator-cluster-role-binding>
> <
http://github.com/cryostatio/cryostat-operator//config/default?ref=v1.0.0
> > <
http://operator.cryostat.io/v1beta1
> > <
http://nginx.ingress.kubernetes.io/backend-protocol
> > <
http://nginx.ingress.kubernetes.io/backend-protocol
> > <
http://nginx.ingress.kubernetes.io/backend-protocol
> <
https://groups.google.com/d/msgid/cryostat-development/730d83ed-431e-4bd3-8d24-b97576571255n%40googlegroups.com?utm_medium=email&utm_source=footer
> <
https://groups.google.com/d/msgid/cryostat-development/730d83ed-431e-4bd3-8d24-b97576571255n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
https://groups.google.com/d/msgid/cryostat-development/e22b45b2-0004-4820-b1f8-e1ab50449f4fn%40googlegroups.com
> <
https://groups.google.com/d/msgid/cryostat-development/e22b45b2-0004-4820-b1f8-e1ab50449f4fn%40googlegroups.com?utm_medium=email&utm_source=footer>.