apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-78.ec2.internal
      uid: 45786f0c-c6e7-4414-86be-f330c3fa735a
    resourceVersion: "14552"
    uid: 40af6d40-ab28-476b-aa98-90f5eca34265
  spec:
    sourcePod: network-check-source-869dcfcdcd-h26xn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:29:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.005124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:29:10Z"
    - latency: 1.19141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:28:10Z"
    - latency: 1.28315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:27:10Z"
    - latency: 1.677733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:26:10Z"
    - latency: 946.666µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:25:10Z"
    - latency: 1.001355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:24:10Z"
    - latency: 1.120721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-78.ec2.internal
      uid: 45786f0c-c6e7-4414-86be-f330c3fa735a
    resourceVersion: "16590"
    uid: 388f8a19-7c3b-441a-b44d-fea277526e07
  spec:
    sourcePod: network-check-source-869dcfcdcd-h26xn
    targetEndpoint: a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:10Z"
      message: 'load-balancer-api-external: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.443456ms
      message: 'load-balancer-api-external: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:34:10Z"
    - latency: 12.218638ms
      message: 'load-balancer-api-external: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:34:10Z"
    - latency: 5.20382ms
      message: 'load-balancer-api-external: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:33:10Z"
    - latency: 15.585164ms
      message: 'load-balancer-api-external: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:33:10Z"
    - latency: 4.451705ms
      message: 'load-balancer-api-external: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:32:10Z"
    - latency: 9.459903ms
      message: 'load-balancer-api-external: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:32:10Z"
    - latency: 5.508814ms
      message: 'load-balancer-api-external: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:31:10Z"
    - latency: 9.177079ms
      message: 'load-balancer-api-external: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:31:10Z"
    - latency: 5.018328ms
      message: 'load-balancer-api-external: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:30:10Z"
    - latency: 10.448654ms
      message: 'load-balancer-api-external: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-78.ec2.internal
      uid: 45786f0c-c6e7-4414-86be-f330c3fa735a
    resourceVersion: "16591"
    uid: 2be9099f-fcb3-4c5e-b7e0-2e8b59172752
  spec:
    sourcePod: network-check-source-869dcfcdcd-h26xn
    targetEndpoint: a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:10Z"
      message: 'load-balancer-api-internal: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.291274ms
      message: 'load-balancer-api-internal: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:34:10Z"
    - latency: 12.249788ms
      message: 'load-balancer-api-internal: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:34:10Z"
    - latency: 5.191806ms
      message: 'load-balancer-api-internal: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:33:10Z"
    - latency: 15.638903ms
      message: 'load-balancer-api-internal: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:33:10Z"
    - latency: 4.414275ms
      message: 'load-balancer-api-internal: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:32:10Z"
    - latency: 9.515397ms
      message: 'load-balancer-api-internal: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:32:10Z"
    - latency: 5.884365ms
      message: 'load-balancer-api-internal: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:31:10Z"
    - latency: 9.186744ms
      message: 'load-balancer-api-internal: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:31:10Z"
    - latency: 5.00641ms
      message: 'load-balancer-api-internal: tcp connection to a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:30:10Z"
    - latency: 10.546832ms
      message: 'load-balancer-api-internal: resolved host name a86acadb0375643fea1464d76a469f72-1a8c2420cfbfe533.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-78-to-network-check-target-ip-10-0-130-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-78.ec2.internal
      uid: 45786f0c-c6e7-4414-86be-f330c3fa735a
    resourceVersion: "14551"
    uid: f736cc35-2f86-41de-b0c0-4d27f723d04e
  spec:
    sourcePod: network-check-source-869dcfcdcd-h26xn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:29:10Z"
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.203696ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:29:10Z"
    - latency: 2.064259ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:28:10Z"
    - latency: 2.385434ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:27:10Z"
    - latency: 2.177361ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:26:10Z"
    - latency: 2.158722ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:25:10Z"
    - latency: 1.956948ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:24:10Z"
    - latency: 1.996203ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-78-to-network-check-target-ip-10-0-133-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-78.ec2.internal
      uid: 45786f0c-c6e7-4414-86be-f330c3fa735a
    resourceVersion: "14549"
    uid: 4dcd681a-40d7-4d6a-9786-861cf5305d52
  spec:
    sourcePod: network-check-source-869dcfcdcd-h26xn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:29:10Z"
      message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.714065ms
      message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:29:10Z"
    - latency: 1.410441ms
      message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:28:10Z"
    - latency: 1.276768ms
      message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:27:10Z"
    - latency: 729.578µs
      message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:26:10Z"
    - latency: 821.221µs
      message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:25:10Z"
    - latency: 898.022µs
      message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:24:10Z"
    - latency: 997.75µs
      message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-78-to-network-check-target-ip-10-0-140-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-78.ec2.internal
      uid: 45786f0c-c6e7-4414-86be-f330c3fa735a
    resourceVersion: "14550"
    uid: 9fc6a1c6-c421-4e42-b768-99a82e25c869
  spec:
    sourcePod: network-check-source-869dcfcdcd-h26xn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:29:10Z"
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.196064ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:29:10Z"
    - latency: 2.202352ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:28:10Z"
    - latency: 1.955704ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:27:10Z"
    - latency: 2.04582ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:26:10Z"
    - latency: 2.111631ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:25:10Z"
    - latency: 1.99814ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:24:10Z"
    - latency: 2.118985ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-78.ec2.internal
      uid: 45786f0c-c6e7-4414-86be-f330c3fa735a
    resourceVersion: "16588"
    uid: ac060f56-23ea-4232-8d0d-82039bc927a3
  spec:
    sourcePod: network-check-source-869dcfcdcd-h26xn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 842.994µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:34:10Z"
    - latency: 1.750686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:34:10Z"
    - latency: 852.11µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:33:10Z"
    - latency: 1.607418ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:33:10Z"
    - latency: 1.360091ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:32:10Z"
    - latency: 1.81037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:32:10Z"
    - latency: 817.644µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:31:10Z"
    - latency: 2.001984ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:31:10Z"
    - latency: 900.795µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:30:10Z"
    - latency: 2.050362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:30:10Z"
kind: List
metadata:
  resourceVersion: ""