apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:37:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-133-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-133.ec2.internal
      uid: ca8fac1b-30a8-4a47-9670-565f82d6c76e
    resourceVersion: "14194"
    uid: 82506c79-8409-4e70-9578-19b51867a0a8
  spec:
    sourcePod: network-check-source-7d88cb55d8-pc59k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:44:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.299635ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:39Z"
    - latency: 1.192874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:39Z"
    - latency: 1.034226ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:39Z"
    - latency: 928.616µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:39Z"
    - latency: 1.075229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:40:39Z"
    - latency: 989.701µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:39:39Z"
    - latency: 1.311786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:38:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:37:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-133-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-133.ec2.internal
      uid: ca8fac1b-30a8-4a47-9670-565f82d6c76e
    resourceVersion: "15937"
    uid: 6c5eb2de-1a3f-48bd-aad0-3a1c02045e12
  spec:
    sourcePod: network-check-source-7d88cb55d8-pc59k
    targetEndpoint: abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:43:39Z"
      message: 'load-balancer-api-external: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.807864ms
      message: 'load-balancer-api-external: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:49:39Z"
    - latency: 7.404377ms
      message: 'load-balancer-api-external: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:49:39Z"
    - latency: 5.43252ms
      message: 'load-balancer-api-external: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:48:39Z"
    - latency: 7.52401ms
      message: 'load-balancer-api-external: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:48:39Z"
    - latency: 4.839352ms
      message: 'load-balancer-api-external: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:47:39Z"
    - latency: 7.818233ms
      message: 'load-balancer-api-external: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:47:39Z"
    - latency: 5.763347ms
      message: 'load-balancer-api-external: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:46:39Z"
    - latency: 7.066565ms
      message: 'load-balancer-api-external: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:46:39Z"
    - latency: 4.917353ms
      message: 'load-balancer-api-external: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:39Z"
    - latency: 6.764052ms
      message: 'load-balancer-api-external: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:45:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:37:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-133-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-133.ec2.internal
      uid: ca8fac1b-30a8-4a47-9670-565f82d6c76e
    resourceVersion: "15936"
    uid: b585ec11-af5f-4aaa-a5e8-ba4fe231f087
  spec:
    sourcePod: network-check-source-7d88cb55d8-pc59k
    targetEndpoint: abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:43:39Z"
      message: 'load-balancer-api-internal: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.66952ms
      message: 'load-balancer-api-internal: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:49:39Z"
    - latency: 7.376585ms
      message: 'load-balancer-api-internal: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:49:39Z"
    - latency: 5.870098ms
      message: 'load-balancer-api-internal: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:48:39Z"
    - latency: 7.56013ms
      message: 'load-balancer-api-internal: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:48:39Z"
    - latency: 5.733224ms
      message: 'load-balancer-api-internal: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:47:39Z"
    - latency: 7.894002ms
      message: 'load-balancer-api-internal: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:47:39Z"
    - latency: 5.66106ms
      message: 'load-balancer-api-internal: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:46:39Z"
    - latency: 7.091005ms
      message: 'load-balancer-api-internal: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:46:39Z"
    - latency: 4.87618ms
      message: 'load-balancer-api-internal: tcp connection to abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:39Z"
    - latency: 6.805089ms
      message: 'load-balancer-api-internal: resolved host name abf94124411674f95937cc6266d2c5a8-f9f28ce481624b2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:45:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:37:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-133-to-network-check-target-ip-10-0-134-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-133.ec2.internal
      uid: ca8fac1b-30a8-4a47-9670-565f82d6c76e
    resourceVersion: "14191"
    uid: 16fc30a2-36d7-4921-95ec-d0dd2e3e03af
  spec:
    sourcePod: network-check-source-7d88cb55d8-pc59k
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:44:39Z"
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.888µs
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:39Z"
    - latency: 1.145089ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:39Z"
    - latency: 2.221638ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:39Z"
    - latency: 769.844µs
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:39Z"
    - latency: 980.666µs
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:40:39Z"
    - latency: 921.884µs
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:39:39Z"
    - latency: 2.50655ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:38:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:37:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-133-to-network-check-target-ip-10-0-143-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-133.ec2.internal
      uid: ca8fac1b-30a8-4a47-9670-565f82d6c76e
    resourceVersion: "14192"
    uid: 6f70be52-c5e3-4626-b431-d8afc8740683
  spec:
    sourcePod: network-check-source-7d88cb55d8-pc59k
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:44:39Z"
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.329141ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:39Z"
    - latency: 2.268751ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:39Z"
    - latency: 2.095984ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:39Z"
    - latency: 2.159841ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:39Z"
    - latency: 1.877966ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:40:39Z"
    - latency: 2.070197ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:39:39Z"
    - latency: 2.496091ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:38:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:37:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-133-to-network-check-target-ip-10-0-143-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-133.ec2.internal
      uid: ca8fac1b-30a8-4a47-9670-565f82d6c76e
    resourceVersion: "14193"
    uid: e7073449-13d9-4e96-868c-ad7ccacd9120
  spec:
    sourcePod: network-check-source-7d88cb55d8-pc59k
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:44:39Z"
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.330239ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:39Z"
    - latency: 2.325133ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:39Z"
    - latency: 2.165747ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:39Z"
    - latency: 2.345125ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:39Z"
    - latency: 2.410988ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:40:39Z"
    - latency: 2.192451ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:39:39Z"
    - latency: 2.571051ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:38:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:37:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-133-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-133.ec2.internal
      uid: ca8fac1b-30a8-4a47-9670-565f82d6c76e
    resourceVersion: "15935"
    uid: d7315c48-8642-401c-8a3a-835978ccc11f
  spec:
    sourcePod: network-check-source-7d88cb55d8-pc59k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:43:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.866µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:49:39Z"
    - latency: 2.772031ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:49:39Z"
    - latency: 1.060352ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:48:39Z"
    - latency: 2.148647ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:48:39Z"
    - latency: 1.003304ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:47:39Z"
    - latency: 2.523511ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:47:39Z"
    - latency: 913.228µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:46:39Z"
    - latency: 2.214711ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:46:39Z"
    - latency: 1.145218ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:39Z"
    - latency: 1.793814ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:45:39Z"
kind: List
metadata:
  resourceVersion: ""