apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:34:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3a259ac8-6a52-4083-95f2-aa4485d5baca
    resourceVersion: "23425"
    uid: 80f9bce1-dad1-4efe-917e-45947aee1615
  spec:
    sourcePod: network-check-source-8894fc9bd-z9djn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T19:41:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.217959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:41:30Z"
    - latency: 1.021698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 1.618356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 1.209207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 1.021664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 1.696535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:36:30Z"
    - latency: 912.046µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:35:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:34:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3a259ac8-6a52-4083-95f2-aa4485d5baca
    resourceVersion: "22252"
    uid: 618eeafa-625a-4088-9f24-2db5210186ce
  spec:
    sourcePod: network-check-source-8894fc9bd-z9djn
    targetEndpoint: ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T19:40:31Z"
      message: 'load-balancer-api-external: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.940598ms
      message: 'load-balancer-api-external: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 8.322856ms
      message: 'load-balancer-api-external: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 4.426419ms
      message: 'load-balancer-api-external: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 8.648914ms
      message: 'load-balancer-api-external: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 4.919112ms
      message: 'load-balancer-api-external: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 8.817616ms
      message: 'load-balancer-api-external: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 4.614495ms
      message: 'load-balancer-api-external: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 8.720995ms
      message: 'load-balancer-api-external: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 3.950542ms
      message: 'load-balancer-api-external: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:36:31Z"
    - latency: 10.742461ms
      message: 'load-balancer-api-external: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:36:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:34:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3a259ac8-6a52-4083-95f2-aa4485d5baca
    resourceVersion: "22251"
    uid: 3532a227-798e-45d5-8c31-9c0b6713d214
  spec:
    sourcePod: network-check-source-8894fc9bd-z9djn
    targetEndpoint: ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T19:40:31Z"
      message: 'load-balancer-api-internal: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.941441ms
      message: 'load-balancer-api-internal: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 8.306875ms
      message: 'load-balancer-api-internal: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 5.341573ms
      message: 'load-balancer-api-internal: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 8.714996ms
      message: 'load-balancer-api-internal: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 4.685342ms
      message: 'load-balancer-api-internal: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 8.75858ms
      message: 'load-balancer-api-internal: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 4.66315ms
      message: 'load-balancer-api-internal: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 8.64178ms
      message: 'load-balancer-api-internal: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 3.969338ms
      message: 'load-balancer-api-internal: tcp connection to ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:36:31Z"
    - latency: 10.818234ms
      message: 'load-balancer-api-internal: resolved host name ae2a61e8933b44875b465826cd149d6d-86a1e1a8389b150a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:36:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:34:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-ip-10-0-129-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3a259ac8-6a52-4083-95f2-aa4485d5baca
    resourceVersion: "23422"
    uid: 48cd8ca5-5019-4e20-82a0-49be54547f70
  spec:
    sourcePod: network-check-source-8894fc9bd-z9djn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T19:41:30Z"
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.217919ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:41:30Z"
    - latency: 717.545µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 947.57µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 812.077µs
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 1.283081ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 1.596526ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:36:30Z"
    - latency: 1.118658ms
      message: 'network-check-target-ip-10-0-129-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:35:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:34:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-ip-10-0-133-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3a259ac8-6a52-4083-95f2-aa4485d5baca
    resourceVersion: "23423"
    uid: c64dd60a-1957-4ab0-aea1-a1a044defd1a
  spec:
    sourcePod: network-check-source-8894fc9bd-z9djn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T19:41:30Z"
      message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.672515ms
      message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:41:30Z"
    - latency: 1.777214ms
      message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 1.792266ms
      message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 2.003638ms
      message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 2.047678ms
      message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 2.420248ms
      message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:36:30Z"
    - latency: 2.146541ms
      message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:35:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:34:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-ip-10-0-133-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3a259ac8-6a52-4083-95f2-aa4485d5baca
    resourceVersion: "23424"
    uid: 33675339-e83d-4f6c-a7bc-bd00bf652643
  spec:
    sourcePod: network-check-source-8894fc9bd-z9djn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T19:41:30Z"
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.045117ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:41:30Z"
    - latency: 1.93125ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 2.069524ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 2.490072ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 1.982597ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 1.936867ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:36:30Z"
    - latency: 1.954882ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:35:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:34:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-155-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-155.ec2.internal
      uid: 3a259ac8-6a52-4083-95f2-aa4485d5baca
    resourceVersion: "22249"
    uid: 2497aa63-98be-4272-b593-e02add04ad51
  spec:
    sourcePod: network-check-source-8894fc9bd-z9djn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T19:40:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 830.251µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 1.755415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:40:30Z"
    - latency: 800.51µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 1.948704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:39:30Z"
    - latency: 1.02181ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 2.525483ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:38:30Z"
    - latency: 853.624µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 2.125651ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:37:30Z"
    - latency: 1.02513ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T19:36:30Z"
    - latency: 2.838322ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T19:36:30Z"
kind: List
metadata:
  resourceVersion: ""