This message was deleted.

Hello @Kim Ted Welcome back! We made significant changes since the 0.4.x version to simplify the installation process and more modular architecture. For the ingress-related issue, I will wait for one of our teammates to help answer you. They are more experienced than I am

@Kim Ted Hi, have you verified that the installation of yatai-deployment is working according to this document? https://docs.bentoml.org/projects/yatai/en/latest/installation/yatai_deployment.html#verify-the-yatai-deployment-installation

@Xipeng Guan Hello xipeng! yes i went into the exact link u mentioned. my k8s version is "v1.24.3" • DEVEL=true bash <(curl -s "https://raw.githubusercontent.com/bentoml/yatai/main/scripts/quick-install-yatai.sh") • DEVEL=true bash <(curl -s "https://raw.githubusercontent.com/bentoml/yatai-deployment/main/scripts/quick-install-yatai-deployment.sh")

@Kim Ted I am curious about the logs of the default-domain job:

kubectl -n yatai-deployment logs -f job/yatai-deployment-default-domain

@Xipeng Guan i found the similar log like the documents yesterday. but it doesn't come up now. think i configured something wrong in my test k8s cluster. wil reinstall the whole yatai. yatai-deployment and let u know with the log

[bigdata@k8smaster1 root]$ k get job -n yatai-deployment
NAME                              COMPLETIONS   DURATION   AGE
yatai-deployment-default-domain   0/1           2d16h      2d16h
[bigdata@k8smaster1 root]$ k logs yatai-deployment-default-domain  -n yatai-deployment
Error from server (NotFound): pods "yatai-deployment-default-domain" not found

@Kim Ted your command is incorrect, do not ignore the

job/

prefix:

nothing comes up with the log

[bigdata@k8smaster1 root]$ kubectl -n yatai-deployment logs -f job/yatai-deployment-default-domain

Got, I want to known the contents of configmap network:

kubectl -n yatai-deployment get cm network -o yaml

didnt put foo:bar

[bigdata@k8smaster1 root]$ kubectl -n yatai-deployment get cm network -o yaml
apiVersion: v1
data:
  ingress-class: nginx
kind: ConfigMap
metadata:
  annotations:
    <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: yatai-deployment
    <http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: yatai-deployment
  creationTimestamp: "2022-10-04T16:36:30Z"
  labels:
    <http://app.kubernetes.io/instance|app.kubernetes.io/instance>: yatai-deployment
    <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: Helm
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: yatai-deployment
    <http://app.kubernetes.io/version|app.kubernetes.io/version>: 1.0.0-a2
    <http://helm.sh/chart|helm.sh/chart>: yatai-deployment-1.0.0-a2
  name: network
  namespace: yatai-deployment
  resourceVersion: "23030212"
  uid: 91ecc7df-ef2f-4761-b21f-5a60955158dd

@Kim Ted It's very weird, can you rerun the default-domain job?

cat <<EOF | kubectl apply -f -
apiVersion: batch/v1
kind: Job
metadata:
  name: yatai-deployment-default-domain-test
  namespace: yatai-deployment
spec:
  template:
    metadata:
      annotations:
        <http://sidecar.istio.io/inject|sidecar.istio.io/inject>: "false"
      labels:
        app: yatai-default-domain-test
    spec:
      containers:
      - env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: SYSTEM_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        image: <http://quay.io/bentoml/yatai-default-domain:0.0.2|quay.io/bentoml/yatai-default-domain:0.0.2>
        imagePullPolicy: IfNotPresent
        name: default-domain
        resources:
          limits:
            cpu: "1"
            memory: 1000Mi
          requests:
            cpu: 100m
            memory: 100Mi
      restartPolicy: Never
      schedulerName: default-scheduler
      serviceAccount: yatai-deployment
      serviceAccountName: yatai-deployment
EOF

log is coming up

[bigdata@k8smaster1 root]$ cat <<EOF | kubectl apply -f -
> apiVersion: batch/v1
      annotations:
        <http://sidecar.istio.io/inject|sidecar.istio.io/inject>: "false"
      labels:
        app: yatai-default-domain-test
> kind: Job
    spec:
      containers:
      - env:
> metadata:
        - name: POD_NAME
          valueFrom:
>   name: yatai-deployment-default-domain-test
>   namespace: yatai-deployment
> spec:
>   template:
>     metadata:
>       annotations:
>         <http://sidecar.istio.io/inject|sidecar.istio.io/inject>: "false"
>       labels:
>         app: yatai-default-domain-test
>     spec:
>       containers:
>       - env:
>         - name: POD_NAME
>           valueFrom:
>             fieldRef:
>               apiVersion: v1
>               fieldPath: metadata.name
>         - name: SYSTEM_NAMESPACE
>           valueFrom:
>             fieldRef:
>               apiVersion: v1
>               fieldPath: metadata.namespace
>         image: <http://quay.io/bentoml/yatai-default-domain:0.0.2|quay.io/bentoml/yatai-default-domain:0.0.2>
>         imagePullPolicy: IfNotPresent
>         name: default-domain
>         resources:
>           limits:
>             cpu: "1"
>             memory: 1000Mi
>           requests:
>             cpu: 100m
>             memory: 100Mi
>       restartPolicy: Never
>       schedulerName: default-scheduler
>       serviceAccount: yatai-deployment
>       serviceAccountName: yatai-deployment
> EOF
job.batch/yatai-deployment-default-domain-test created

[bigdata@k8smaster1 root]$ k get job yatai-deployment-default-domain-test -n yatai-deployment
NAME                                   COMPLETIONS   DURATION   AGE
yatai-deployment-default-domain-test   0/1           23s        23s

[bigdata@k8smaster1 root]$ kubectl -n yatai-deployment logs -f job/yatai-deployment-default-domain-test
time="2022-10-07T08:54:10Z" level=info msg="Creating ingress default-domain- to get a ingress IP automatically"
time="2022-10-07T08:54:10Z" level=info msg="Waiting for ingress default-domain-l2bd2 to be ready"

@Kim Ted This error message you can ignore:

default-domain-service:3000 (<error: endpoints "default-domain-service" not found>)

@Xipeng Guan ah thanks. that was what i was curious of ingress. thanks!

@Kim Ted This log will tell you the final automatically generated domain suffix, and you can wait a few minutes to get the entire log content

kubectl -n yatai-deployment logs -f job/yatai-deployment-default-domain-test