apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T16:02:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-152-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-152.ec2.internal
      uid: d10eaa7d-1d5f-46c9-a3c2-3c630bb1636f
    resourceVersion: "22452"
    uid: c3ffbc62-f7fa-4c12-a686-bd4b663c90c0
  spec:
    sourcePod: network-check-source-8894fc9bd-v59wb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T16:09:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 963.827µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:09:21Z"
    - latency: 1.506913ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 985.253µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 1.021336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 1.165824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 1.172139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:04:21Z"
    - latency: 984.281µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:03:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T16:02:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-152-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-152.ec2.internal
      uid: d10eaa7d-1d5f-46c9-a3c2-3c630bb1636f
    resourceVersion: "20896"
    uid: 2c2cbd06-d38a-4786-8625-354a5c01741e
  spec:
    sourcePod: network-check-source-8894fc9bd-v59wb
    targetEndpoint: a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T16:08:21Z"
      message: 'load-balancer-api-external: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.589485ms
      message: 'load-balancer-api-external: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 7.870321ms
      message: 'load-balancer-api-external: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 5.669082ms
      message: 'load-balancer-api-external: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 7.234334ms
      message: 'load-balancer-api-external: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 4.904236ms
      message: 'load-balancer-api-external: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 8.776156ms
      message: 'load-balancer-api-external: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 5.621083ms
      message: 'load-balancer-api-external: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 7.366661ms
      message: 'load-balancer-api-external: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 4.898076ms
      message: 'load-balancer-api-external: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:04:21Z"
    - latency: 7.894178ms
      message: 'load-balancer-api-external: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:04:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T16:02:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-152-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-152.ec2.internal
      uid: d10eaa7d-1d5f-46c9-a3c2-3c630bb1636f
    resourceVersion: "20895"
    uid: 1874dba9-c2b7-438c-9f4d-be1a74f27da8
  spec:
    sourcePod: network-check-source-8894fc9bd-v59wb
    targetEndpoint: a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T16:08:21Z"
      message: 'load-balancer-api-internal: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.74516ms
      message: 'load-balancer-api-internal: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 7.390696ms
      message: 'load-balancer-api-internal: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 5.679886ms
      message: 'load-balancer-api-internal: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 7.183999ms
      message: 'load-balancer-api-internal: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 4.781564ms
      message: 'load-balancer-api-internal: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 8.687547ms
      message: 'load-balancer-api-internal: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 5.641849ms
      message: 'load-balancer-api-internal: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 7.39646ms
      message: 'load-balancer-api-internal: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 4.925984ms
      message: 'load-balancer-api-internal: tcp connection to a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:04:21Z"
    - latency: 7.757251ms
      message: 'load-balancer-api-internal: resolved host name a5b1eb52ea1864bac885cc2cd4752bea-a92d3f43e1ea0320.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:04:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T16:02:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-152-to-network-check-target-ip-10-0-132-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-152.ec2.internal
      uid: d10eaa7d-1d5f-46c9-a3c2-3c630bb1636f
    resourceVersion: "22451"
    uid: 4af466f8-8b06-4ead-b555-60a6de0d0866
  spec:
    sourcePod: network-check-source-8894fc9bd-v59wb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T16:09:21Z"
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.394122ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:09:21Z"
    - latency: 2.36429ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 2.168873ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 2.613461ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 2.42345ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 2.296774ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:04:21Z"
    - latency: 2.44388ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:03:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T16:02:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-152-to-network-check-target-ip-10-0-135-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-152.ec2.internal
      uid: d10eaa7d-1d5f-46c9-a3c2-3c630bb1636f
    resourceVersion: "22449"
    uid: c617014b-4b63-45df-bb6c-5f6692db9bb2
  spec:
    sourcePod: network-check-source-8894fc9bd-v59wb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T16:09:21Z"
      message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.196107ms
      message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:09:21Z"
    - latency: 1.511561ms
      message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 899.178µs
      message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 910.948µs
      message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 1.096438ms
      message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 931.851µs
      message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:04:21Z"
    - latency: 1.119258ms
      message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:03:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T16:02:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-152-to-network-check-target-ip-10-0-135-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-152.ec2.internal
      uid: d10eaa7d-1d5f-46c9-a3c2-3c630bb1636f
    resourceVersion: "22450"
    uid: 3a6dd930-cbc5-4ee1-9f2d-7242a8394071
  spec:
    sourcePod: network-check-source-8894fc9bd-v59wb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T16:09:21Z"
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.231409ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:09:21Z"
    - latency: 1.974797ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 2.016206ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 2.120468ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 2.234827ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 1.969237ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:04:21Z"
    - latency: 2.261552ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:03:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T16:02:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-152-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-152.ec2.internal
      uid: d10eaa7d-1d5f-46c9-a3c2-3c630bb1636f
    resourceVersion: "20893"
    uid: f53caa73-29f9-40e6-a4aa-1b7f01d7a4e3
  spec:
    sourcePod: network-check-source-8894fc9bd-v59wb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T16:08:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 790.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 2.093393ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:08:21Z"
    - latency: 867.07µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 1.62422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:07:21Z"
    - latency: 892.572µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 2.104503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:06:21Z"
    - latency: 850.771µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 1.911938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:05:21Z"
    - latency: 817.396µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:04:21Z"
    - latency: 1.702078ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:04:21Z"
kind: List
metadata:
  resourceVersion: ""