apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T19:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 5ff2a8da-753a-4147-bc29-4f76286de5f5
    resourceVersion: "23673"
    uid: ba53c993-c2b9-43b0-b828-4a78cc8c1ebc
  spec:
    sourcePod: network-check-source-8894fc9bd-snltq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T19:37:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.05584ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:37:03Z"
    - latency: 2.458052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 1.084429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 952.631µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 965.382µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 851.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:32:03Z"
    - latency: 828.826µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:31:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T19:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 5ff2a8da-753a-4147-bc29-4f76286de5f5
    resourceVersion: "22571"
    uid: b1f9e9f5-7042-4022-b864-2c3483f918d8
  spec:
    sourcePod: network-check-source-8894fc9bd-snltq
    targetEndpoint: ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T19:36:03Z"
      message: 'load-balancer-api-external: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.393899ms
      message: 'load-balancer-api-external: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 9.404759ms
      message: 'load-balancer-api-external: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 4.695056ms
      message: 'load-balancer-api-external: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 7.04338ms
      message: 'load-balancer-api-external: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 5.197592ms
      message: 'load-balancer-api-external: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 6.426636ms
      message: 'load-balancer-api-external: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 4.618612ms
      message: 'load-balancer-api-external: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 7.103612ms
      message: 'load-balancer-api-external: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 4.247338ms
      message: 'load-balancer-api-external: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:32:03Z"
    - latency: 7.822304ms
      message: 'load-balancer-api-external: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:32:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T19:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 5ff2a8da-753a-4147-bc29-4f76286de5f5
    resourceVersion: "22570"
    uid: 874da254-b2d5-47b9-a8c3-2377705a3976
  spec:
    sourcePod: network-check-source-8894fc9bd-snltq
    targetEndpoint: ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T19:36:03Z"
      message: 'load-balancer-api-internal: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.744209ms
      message: 'load-balancer-api-internal: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 9.22944ms
      message: 'load-balancer-api-internal: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 4.653141ms
      message: 'load-balancer-api-internal: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 7.111551ms
      message: 'load-balancer-api-internal: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 4.051204ms
      message: 'load-balancer-api-internal: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 6.489078ms
      message: 'load-balancer-api-internal: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 4.428912ms
      message: 'load-balancer-api-internal: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 7.080064ms
      message: 'load-balancer-api-internal: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 4.530244ms
      message: 'load-balancer-api-internal: tcp connection to ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:32:03Z"
    - latency: 7.200157ms
      message: 'load-balancer-api-internal: resolved host name ae2e621b80d424907a5647088b1ae6d6-0c1d4d5d0713b0cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:32:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T19:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-network-check-target-ip-10-0-131-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 5ff2a8da-753a-4147-bc29-4f76286de5f5
    resourceVersion: "23672"
    uid: 4d82322b-fbf2-48e0-b994-a2c801905678
  spec:
    sourcePod: network-check-source-8894fc9bd-snltq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T19:37:03Z"
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.415662ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:37:03Z"
    - latency: 2.645405ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 990.083µs
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 1.589422ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 911.809µs
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 1.04779ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:32:03Z"
    - latency: 1.722583ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:31:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T19:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-network-check-target-ip-10-0-132-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 5ff2a8da-753a-4147-bc29-4f76286de5f5
    resourceVersion: "23670"
    uid: f5b9905e-c212-419a-b85d-103df105267b
  spec:
    sourcePod: network-check-source-8894fc9bd-snltq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T19:37:03Z"
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.554229ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:37:03Z"
    - latency: 3.153305ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 2.172987ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 2.17718ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 2.151619ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 1.844626ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:32:03Z"
    - latency: 2.392377ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:31:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T19:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-network-check-target-ip-10-0-135-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 5ff2a8da-753a-4147-bc29-4f76286de5f5
    resourceVersion: "23671"
    uid: b9c97250-4e98-4221-afbe-03d1ab40a5ef
  spec:
    sourcePod: network-check-source-8894fc9bd-snltq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T19:37:03Z"
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.702869ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:37:03Z"
    - latency: 3.510097ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 2.469455ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 2.878158ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 2.351358ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 2.453387ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:32:03Z"
    - latency: 2.415976ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:31:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T19:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 5ff2a8da-753a-4147-bc29-4f76286de5f5
    resourceVersion: "22569"
    uid: cba93bf0-cd33-4dde-b32d-8ad0294be342
  spec:
    sourcePod: network-check-source-8894fc9bd-snltq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T19:36:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.65479ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 1.498405ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:36:03Z"
    - latency: 854.262µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 1.777776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:35:03Z"
    - latency: 1.077049ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 1.689312ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:34:03Z"
    - latency: 787.811µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 1.620141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:33:03Z"
    - latency: 1.172405ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T19:32:03Z"
    - latency: 1.153643ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T19:32:03Z"
kind: List
metadata:
  resourceVersion: ""