apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: 20303788-c5fe-454c-aa20-c0dbc9d6a515 resourceVersion: "55057" uid: 9153e822-5f72-496a-8d86-6cb495dd9e45 spec: sourcePod: network-check-source-869dcfcdcd-c9zm4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T21:20:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.852807ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:06Z" - latency: 987.982µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:06Z" - latency: 986.363µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:06Z" - latency: 1.052848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:06Z" - latency: 1.559008ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:06Z" - latency: 1.281061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:06Z" - latency: 931.4µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:06Z" - latency: 1.021552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:06Z" - latency: 808.034µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:06Z" - latency: 926.693µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: 20303788-c5fe-454c-aa20-c0dbc9d6a515 resourceVersion: "50078" uid: 09b64223-014b-40d3-8612-15629dfff570 spec: sourcePod: network-check-source-869dcfcdcd-c9zm4 targetEndpoint: aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:19:06Z" message: 'load-balancer-api-external: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.655747ms message: 'load-balancer-api-external: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:06Z" - latency: 8.896479ms message: 'load-balancer-api-external: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:43:06Z" - latency: 4.279001ms message: 'load-balancer-api-external: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:06Z" - latency: 7.384408ms message: 'load-balancer-api-external: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:42:06Z" - latency: 5.874955ms message: 'load-balancer-api-external: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:06Z" - latency: 7.488193ms message: 'load-balancer-api-external: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:41:06Z" - latency: 5.727779ms message: 'load-balancer-api-external: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:06Z" - latency: 9.231635ms message: 'load-balancer-api-external: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:40:06Z" - latency: 6.227441ms message: 'load-balancer-api-external: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:06Z" - latency: 9.047828ms message: 'load-balancer-api-external: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: 20303788-c5fe-454c-aa20-c0dbc9d6a515 resourceVersion: "50079" uid: 435b73c2-af4f-4790-bde0-25957828dcfb spec: sourcePod: network-check-source-869dcfcdcd-c9zm4 targetEndpoint: aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:19:06Z" message: 'load-balancer-api-internal: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.636327ms message: 'load-balancer-api-internal: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:06Z" - latency: 8.874066ms message: 'load-balancer-api-internal: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:43:06Z" - latency: 4.283124ms message: 'load-balancer-api-internal: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:06Z" - latency: 7.337484ms message: 'load-balancer-api-internal: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:42:06Z" - latency: 4.561084ms message: 'load-balancer-api-internal: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:06Z" - latency: 7.432533ms message: 'load-balancer-api-internal: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:41:06Z" - latency: 4.876397ms message: 'load-balancer-api-internal: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:06Z" - latency: 9.203122ms message: 'load-balancer-api-internal: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:40:06Z" - latency: 8.050887ms message: 'load-balancer-api-internal: tcp connection to aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:06Z" - latency: 9.008279ms message: 'load-balancer-api-internal: resolved host name aeb22c2a19df84346b852c18f7c5d08e-9550d1fa94e55544.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-network-check-target-ip-10-0-136-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: 20303788-c5fe-454c-aa20-c0dbc9d6a515 resourceVersion: "55054" uid: 85bddf66-5501-4af1-b496-cd6f3435e6dd spec: sourcePod: network-check-source-869dcfcdcd-c9zm4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:20:06Z" message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.085742ms message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:06Z" - latency: 995.961µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:06Z" - latency: 1.0531ms message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:06Z" - latency: 942.12µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:06Z" - latency: 963.165µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:06Z" - latency: 913.549µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:06Z" - latency: 1.439856ms message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:06Z" - latency: 970.336µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:06Z" - latency: 926.456µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:06Z" - latency: 1.218288ms message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-network-check-target-ip-10-0-136-18 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: 20303788-c5fe-454c-aa20-c0dbc9d6a515 resourceVersion: "55056" uid: 938b7c37-99e7-43aa-80d7-e40edfccda71 spec: sourcePod: network-check-source-869dcfcdcd-c9zm4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:20:06Z" message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.533895ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:06Z" - latency: 2.148441ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:06Z" - latency: 2.506001ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:06Z" - latency: 2.188107ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:06Z" - latency: 2.220778ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:06Z" - latency: 2.534457ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:06Z" - latency: 2.138715ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:06Z" - latency: 2.648067ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:06Z" - latency: 2.315309ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:06Z" - latency: 2.025607ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-network-check-target-ip-10-0-139-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: 20303788-c5fe-454c-aa20-c0dbc9d6a515 resourceVersion: "55055" uid: 47362755-7f56-4734-9373-d1424ab832c2 spec: sourcePod: network-check-source-869dcfcdcd-c9zm4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:20:06Z" message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.186969ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:06Z" - latency: 2.431302ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:06Z" - latency: 2.355972ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:06Z" - latency: 2.613669ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:06Z" - latency: 2.116551ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:06Z" - latency: 2.939186ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:06Z" - latency: 2.081908ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:06Z" - latency: 2.327527ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:06Z" - latency: 2.192921ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:06Z" - latency: 2.278341ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: 20303788-c5fe-454c-aa20-c0dbc9d6a515 resourceVersion: "50077" uid: 1d694581-d4fa-47f0-81e4-e9ad6c698bb5 spec: sourcePod: network-check-source-869dcfcdcd-c9zm4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T21:19:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 785.148µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:06Z" - latency: 1.779945ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:43:06Z" - latency: 1.484032ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:06Z" - latency: 1.675515ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:42:06Z" - latency: 983.663µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:06Z" - latency: 2.020221ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:41:06Z" - latency: 1.283857ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:06Z" - latency: 1.772553ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:40:06Z" - latency: 870.638µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:39:06Z" - latency: 2.309516ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:39:06Z" kind: List metadata: resourceVersion: ""