Jace

@mjace

Joined on Jun 5, 2018

  • 2025/05/14 AI TAM discussion from OCP perspective 2025/04/09 ESG Power monitoring - Kepler 2025/03/12 Technical Supportability Review (TSR) https://docs.google.com/presentation/d/1c7RiuZPjlL5PKL5YEaQAbVI-eoaZKa3FROX64cDLoL8/edit#slide=id.g33cd9ce6bd3_0_0
     Like  Bookmark
  • oc exec -it <pod name> -- bash jcmd -l jmap -dump:[live],format=b,file=[file_path] [PID] Thread dump oc exec -it <pod name> -- bash jcmd -l jstack -l <JAVA_PID> > jstack.out Copy sinopac heapdump ## 用oc dubug 連線到Java Pod所在的節點 oc debug node/<node-name>
     Like  Bookmark
  • !!!此文件目的為驗證服務架構,非生產環境安裝指引!!! Environment and important pre-set OCP 4.16 cluster minio is installed in ns/minio Minio Access Key : tempo Minio Secret Key : supersecret Minio's svc is named minio TempoStack is installed in namespacetempo TempoStack is named sample A OpenTelemetryCollector named otel is installed in ns/istio-system
     Like 1 Bookmark
  • !!!此文件目的為驗證服務架構,非生產環境安裝指引!!! The whole picture of OSSM + Tempo image Environment and important pre-set Resource Hub OCP 4.16 cluster minio is installed in ns/minio Minio Access Key : tempo Minio Secret Key : supersecret Minio's svc is named minio
     Like  Bookmark
  • TAM 服務 誠摯通知您,由於本公司將於 2025 年 2 月 7 日至 2 月 17 日在美國舉辦 Red Hat One 全球年會,期間 TAM 服務將有以下調整。 服務調整說明: TAM 團隊將無法提供實地技術顧問服務 技術支援需求請直接透過 Customer Portal 建立案件,由全球技術支援團隊優先處理 考量時差因素,除緊急狀況外,TAM 將依美國當地工作時間進行案件追蹤 如需 TAM 參與線上會議,建議提前預約安排時段 What's Red Hat One(formerly known as Sales Kickoff & Tech Exchange)
     Like  Bookmark
  • 檔名規則 如果已經開立Case,請以caseID作為檔案前綴 例如 03990809-inspect.local.tar.gz 03990888-must-gather.tar.gz 1. sftp user/password "username" : "rhn-support-jaliang", "token" : "SIVRmyNv", 登入並上傳檔案至red hat sftp
     Like  Bookmark
  • 調整方法 查看啟用FIPS後OCP節點上可用的cipher $ openssl ciphers -v TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD TLS_AES_128_GCM_SHA256 TLSv1.3 Kx=any Au=any Enc=AESGCM(128) Mac=AEAD TLS_AES_128_CCM_SHA256 TLSv1.3 Kx=any Au=any Enc=AESCCM(128) Mac=AEAD ECDHE-ECDSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=ECDSA Enc=AESGCM(256) Mac=AEAD ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD ECDHE-ECDSA-AES256-CCM TLSv1.2 Kx=ECDH Au=ECDSA Enc=AESCCM(256) Mac=AEAD
     Like  Bookmark
  • 待釐清 跟運作正常的Production Quay配置有和不同 網路相同 都是連到OCP的sso SSO 安裝方式 -> SSO Operator 有無開啟Proxy registry.apps.ocp.tsmeg.org.tw
     Like  Bookmark
  • Location / Guide Screenshot 2024-10-08 at 11.26.36 AM Medium https://pebblepusher.com/top-3-boulder-problems-in-red-rocks-the-kraft-boulders-v0-v8/ https://courtandjohn.com/2016/12/05/kraft-boulders-top-8-problems-for-beginners-v0-2/ 租車 image Avis 離MGM Grand最近
     Like  Bookmark
  • [quickcluster@upi-0 ~]$ oc get networkpolicy -o yaml apiVersion: v1 items: - apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: creationTimestamp: "2024-09-04T09:05:50Z" generation: 4 name: allow-ingress namespace: jace
     Like  Bookmark
  • 確認方法1 Creating a simple pod and pvc on the node consistently fails with: Warning FailedMount 1s (x6 over 17s) kubelet MountVolume.SetUp failed for volume "pvc-f5abf781-571f-400a-8d7b-7396297f9e08" : rpc error: code = FailedPrecondition desc = volume ID: "b32d480a-76f7-4607-8313-4c72c9bfa033" does not appear staged to "/var/lib/kubelet/plugins/kubernetes.io/csi/csi.vsphere.vmware.com/3a3fecfcf6c6c61fb2df59da41392ae1d7e972fd0ce582a79bf8ee60b6220aad/globalmount" The mount already exists, using the /dev/mapper device: sh-5.1# mount | grep csi /dev/mapper/36000c29622f0b0506766a70d894fab33 on /var/lib/kubelet/plugins/kubernetes.io/csi/csi.vsphere.vmware.com/3a3fecfcf6c6c61fb2df59da41392ae1d7e972fd0ce582a79bf8ee60b6220aad/globalmount type ext4 (rw,relatime,seclabel) From the vmware-vsphere-csi-driver-node pod logs:
     Like  Bookmark
  • image Ask : 此Linux系統有無異常的錯誤資訊 Answer: 是的,這個 Linux 系統顯示了多個錯誤訊息。以下是一些主要的錯誤和其含義: CRI-O Auto Update Script Failed:​​​crio-wipe.service: Main process exited, code=exited, status=203/EXEC ​​​crio-wipe.service: Failed with result 'exit-code'. CRI-O 的自動更新腳本失敗了。
     Like  Bookmark
  • Pod level apiVersion: v1 kind: Pod metadata: annotations: sidecar.istio.io/inject: "true" name: ubuntu-2 labels: app: ubuntu spec:
     Like  Bookmark
  • kubectl debug -it ephemeral-demo --image=busybox:1.28 --target=ephemeral-demo kubect debug -it <pod_name> --image=<image_as_debug_tool> --target=<target_container_name> ## 原本Pod無 top / ps指令 ❯ oc exec -it caturday-6c5f74f5d6-72zs4 top kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead. Defaulted container "caturday" out of: caturday, debugger-lnwnh (ephem) ERRO[0000] exec failed: unable to start container process: exec: "top": executable file not found in $PATH command terminated with exit code 255 ❯ oc exec -it caturday-6c5f74f5d6-72zs4 ps kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
     Like  Bookmark
  • 準備 Hypervisior 必備kubeconfig VM關機或暫停後OCP失效問題 oc login失敗, kubelet無法連線到api-server 用備份的kubeconfig 登入到sno節點後執行KB內操作 https://access.redhat.com/solutions/4923031 oc 指令正常, 部分pod無法正常啟動, Error message出現multus / OVN相關錯誤
     Like  Bookmark
  • 還原問題 oc apply -f mcp.yaml apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfigPool metadata: name: worker-1 spec: machineConfigSelector:
     Like  Bookmark
  • Prerequisites An OpenShift Cluster (ROSA, ARO, OSD, and OCP 4.x all work) oc helm v3 Installing the Kubernetes Secret Store CSI Create an OpenShift Project to deploy the CSI into oc new-project k8s-secrets-store-csi Set SecurityContextConstraints to allow the CSI driver to run (otherwise the DaemonSet will not be able to create Pods)
     Like  Bookmark
  • Gather node / pod sysctl config sysctl net.netfilter.nf_conntrack_tcp_be_liberal Scale App down to 1, modify the node sysctl setting On node sysctl -w net.netfilter.nf_conntrack_tcp_be_liberal=1 Restart pod, check sysctl config inside pod again. check config inside pod
     Like  Bookmark
  • 0. 環境介紹 Go to the info page click on VScode server link, use password provided in the table to login. Go to info page click on Automation controller link, use username and password provided in the table to login. Go to the Automation controller console and click on jobs under Views. Jobs section will show all triggered job templates status by the EDA. Go back to the VScode server console and open a terminal. Split terminal so that we can execute and observe the command output side by side.
     Like  Bookmark
  • OCP / ACM OpenShift Console URL https://console-openshift-console.apps.cluster-c6wqd.c6wqd.sandbox2982.opentlc.com admin 9Bo7Ul59fEBCFiou AAP https://example-aap.apps.cluster-c6wqd.c6wqd.sandbox2982.opentlc.com/
     Like  Bookmark