apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-116-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-116.ec2.internal
      uid: 5bd37441-b599-4e71-9241-a0e8c0991b94
    resourceVersion: "21979"
    uid: 4a006562-f966-41ef-8a54-bedbf21ffead
  spec:
    sourcePod: network-check-source-56499946bc-tbws5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:22:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.503573ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:22:04Z"
    - latency: 961.755µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 1.238006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 1.310841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 1.258255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 1.147534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:17:04Z"
    - latency: 1.477026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:16:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-116-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-116.ec2.internal
      uid: 5bd37441-b599-4e71-9241-a0e8c0991b94
    resourceVersion: "20719"
    uid: 2de221d5-315b-45fa-9ecf-db8d703af4ba
  spec:
    sourcePod: network-check-source-56499946bc-tbws5
    targetEndpoint: a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:21:04Z"
      message: 'load-balancer-api-external: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.81987ms
      message: 'load-balancer-api-external: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 9.456317ms
      message: 'load-balancer-api-external: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 4.693864ms
      message: 'load-balancer-api-external: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 9.686649ms
      message: 'load-balancer-api-external: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 4.781826ms
      message: 'load-balancer-api-external: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 11.34356ms
      message: 'load-balancer-api-external: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 5.423456ms
      message: 'load-balancer-api-external: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 9.574352ms
      message: 'load-balancer-api-external: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 7.391544ms
      message: 'load-balancer-api-external: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:17:04Z"
    - latency: 8.571ms
      message: 'load-balancer-api-external: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:17:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-116-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-116.ec2.internal
      uid: 5bd37441-b599-4e71-9241-a0e8c0991b94
    resourceVersion: "20721"
    uid: 7da32c00-4539-4e91-a1e2-9c8dfde1311e
  spec:
    sourcePod: network-check-source-56499946bc-tbws5
    targetEndpoint: a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:21:04Z"
      message: 'load-balancer-api-internal: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.823977ms
      message: 'load-balancer-api-internal: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 9.471418ms
      message: 'load-balancer-api-internal: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 4.741656ms
      message: 'load-balancer-api-internal: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 9.667119ms
      message: 'load-balancer-api-internal: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 7.14947ms
      message: 'load-balancer-api-internal: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 11.188103ms
      message: 'load-balancer-api-internal: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 5.391905ms
      message: 'load-balancer-api-internal: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 9.62991ms
      message: 'load-balancer-api-internal: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 7.871302ms
      message: 'load-balancer-api-internal: tcp connection to a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:17:04Z"
    - latency: 8.557608ms
      message: 'load-balancer-api-internal: resolved host name a54ed734287f841bc82b26c4e4ad650f-bc171501f1000d4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:17:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-116-to-network-check-target-ip-10-0-133-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-116.ec2.internal
      uid: 5bd37441-b599-4e71-9241-a0e8c0991b94
    resourceVersion: "21976"
    uid: e3260164-0740-4923-945c-d2bb977e915e
  spec:
    sourcePod: network-check-source-56499946bc-tbws5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:22:04Z"
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.362µs
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:22:04Z"
    - latency: 1.33311ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 1.263231ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 2.662099ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 1.0879ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 1.322139ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:17:04Z"
    - latency: 1.666114ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:16:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-116-to-network-check-target-ip-10-0-138-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-116.ec2.internal
      uid: 5bd37441-b599-4e71-9241-a0e8c0991b94
    resourceVersion: "21978"
    uid: f971c88f-e30a-4d06-b990-b58fbe554326
  spec:
    sourcePod: network-check-source-56499946bc-tbws5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:22:04Z"
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.037609ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:22:04Z"
    - latency: 1.997775ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 1.852205ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 1.77915ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 1.812814ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 1.898432ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:17:04Z"
    - latency: 1.89357ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:16:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-116-to-network-check-target-ip-10-0-143-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-116.ec2.internal
      uid: 5bd37441-b599-4e71-9241-a0e8c0991b94
    resourceVersion: "21977"
    uid: e067e993-3372-44ae-a604-08c12c27ce8d
  spec:
    sourcePod: network-check-source-56499946bc-tbws5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:22:04Z"
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.870792ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:22:04Z"
    - latency: 2.195318ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 2.231059ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 2.890272ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 2.153601ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 2.021263ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:17:04Z"
    - latency: 2.2311ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:16:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-116-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-116.ec2.internal
      uid: 5bd37441-b599-4e71-9241-a0e8c0991b94
    resourceVersion: "20718"
    uid: e24569da-057b-4cfc-b82e-58cc8499444d
  spec:
    sourcePod: network-check-source-56499946bc-tbws5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:21:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.28µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 2.11746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:21:04Z"
    - latency: 834.782µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 1.810114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:20:04Z"
    - latency: 1.025405ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 2.758725ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:19:04Z"
    - latency: 926.601µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 2.116566ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:18:04Z"
    - latency: 823.489µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:17:04Z"
    - latency: 1.90867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:17:04Z"
kind: List
metadata:
  resourceVersion: ""