apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:01:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-58-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-58.ec2.internal uid: e1bab753-a91d-42b5-8f54-0ab79f96b935 resourceVersion: "72424" uid: d18d4866-2801-4019-b3fb-c57080fc14f6 spec: sourcePod: network-check-source-65bdbbff45-7r4b8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-31T23:08:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.828856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:50:17Z" - latency: 854.901µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:49:17Z" - latency: 805.99µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:48:17Z" - latency: 1.090682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:47:17Z" - latency: 897.427µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:46:17Z" - latency: 1.07463ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:45:17Z" - latency: 1.303421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:44:17Z" - latency: 773.188µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:43:17Z" - latency: 920.146µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:42:17Z" - latency: 1.068489ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:41:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:01:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-58-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-58.ec2.internal uid: e1bab753-a91d-42b5-8f54-0ab79f96b935 resourceVersion: "77823" uid: 1f16871d-4581-40b6-8923-e6b7c079aba2 spec: sourcePod: network-check-source-65bdbbff45-7r4b8 targetEndpoint: a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T23:07:17Z" message: 'load-balancer-api-external: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.100048ms message: 'load-balancer-api-external: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:55:17Z" - latency: 7.490183ms message: 'load-balancer-api-external: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:55:17Z" - latency: 5.514463ms message: 'load-balancer-api-external: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:54:17Z" - latency: 8.275065ms message: 'load-balancer-api-external: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:54:17Z" - latency: 10.686293ms message: 'load-balancer-api-external: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:53:17Z" - latency: 6.75942ms message: 'load-balancer-api-external: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:53:17Z" - latency: 5.452368ms message: 'load-balancer-api-external: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:52:17Z" - latency: 6.833918ms message: 'load-balancer-api-external: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:52:17Z" - latency: 5.637356ms message: 'load-balancer-api-external: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:51:17Z" - latency: 6.556845ms message: 'load-balancer-api-external: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:51:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:01:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-58-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-58.ec2.internal uid: e1bab753-a91d-42b5-8f54-0ab79f96b935 resourceVersion: "77822" uid: 95aff8c6-2d39-4a94-a5f5-64b8141c3f38 spec: sourcePod: network-check-source-65bdbbff45-7r4b8 targetEndpoint: a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T23:07:17Z" message: 'load-balancer-api-internal: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.128151ms message: 'load-balancer-api-internal: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:55:17Z" - latency: 7.480904ms message: 'load-balancer-api-internal: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:55:17Z" - latency: 4.756511ms message: 'load-balancer-api-internal: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:54:17Z" - latency: 8.292809ms message: 'load-balancer-api-internal: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:54:17Z" - latency: 5.541594ms message: 'load-balancer-api-internal: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:53:17Z" - latency: 6.682965ms message: 'load-balancer-api-internal: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:53:17Z" - latency: 5.374714ms message: 'load-balancer-api-internal: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:52:17Z" - latency: 6.863561ms message: 'load-balancer-api-internal: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:52:17Z" - latency: 3.872574ms message: 'load-balancer-api-internal: tcp connection to a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:51:17Z" - latency: 6.612985ms message: 'load-balancer-api-internal: resolved host name a9825ca2d6cbc4c0a8cc209121d1658e-6e80bfa909614b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T23:51:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:01:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-58-to-network-check-target-ip-10-0-128-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-58.ec2.internal uid: e1bab753-a91d-42b5-8f54-0ab79f96b935 resourceVersion: "72421" uid: ff610a34-9d36-4b51-8e67-d384ac07513b spec: sourcePod: network-check-source-65bdbbff45-7r4b8 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-31T23:08:17Z" message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.385212ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:50:17Z" - latency: 2.322087ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:49:17Z" - latency: 2.887578ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:48:17Z" - latency: 2.346639ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:47:17Z" - latency: 2.436697ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:46:17Z" - latency: 2.788237ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:45:17Z" - latency: 2.404112ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:44:17Z" - latency: 2.409649ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:43:17Z" - latency: 2.434227ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:42:17Z" - latency: 2.687684ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:41:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:01:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-58-to-network-check-target-ip-10-0-131-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-58.ec2.internal uid: e1bab753-a91d-42b5-8f54-0ab79f96b935 resourceVersion: "72422" uid: d36b6a61-2866-4436-be9b-207836d5f4c3 spec: sourcePod: network-check-source-65bdbbff45-7r4b8 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-31T23:08:17Z" message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.252537ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:50:17Z" - latency: 2.463708ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:49:17Z" - latency: 2.3241ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:48:17Z" - latency: 2.058625ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:47:17Z" - latency: 2.240571ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:46:17Z" - latency: 2.80981ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:45:17Z" - latency: 1.974248ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:44:17Z" - latency: 2.051759ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:43:17Z" - latency: 1.765435ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:42:17Z" - latency: 1.913427ms message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:41:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:01:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-58-to-network-check-target-ip-10-0-137-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-58.ec2.internal uid: e1bab753-a91d-42b5-8f54-0ab79f96b935 resourceVersion: "72423" uid: 23ef5a6c-5bdd-402e-98bc-741347e955cf spec: sourcePod: network-check-source-65bdbbff45-7r4b8 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-31T23:08:17Z" message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002167ms message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:50:17Z" - latency: 885.427µs message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:49:17Z" - latency: 819.042µs message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:48:17Z" - latency: 740.144µs message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:47:17Z" - latency: 1.034058ms message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:46:17Z" - latency: 1.193788ms message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:45:17Z" - latency: 895.524µs message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:44:17Z" - latency: 1.1583ms message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:43:17Z" - latency: 1.526858ms message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:42:17Z" - latency: 1.317787ms message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:41:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:01:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-58-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-58.ec2.internal uid: e1bab753-a91d-42b5-8f54-0ab79f96b935 resourceVersion: "77821" uid: 9b6eb8c1-0f7f-493d-9489-3ce7d20fcfc2 spec: sourcePod: network-check-source-65bdbbff45-7r4b8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-31T23:07:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.177007ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:55:17Z" - latency: 1.915676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T23:55:17Z" - latency: 1.427588ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:54:17Z" - latency: 1.82304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T23:54:17Z" - latency: 886.41µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:53:17Z" - latency: 1.539817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T23:53:17Z" - latency: 1.070664ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:52:17Z" - latency: 1.675824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T23:52:17Z" - latency: 987.733µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T23:51:17Z" - latency: 1.662499ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T23:51:17Z" kind: List metadata: resourceVersion: ""