Skip to content

Commit 4028593

Browse files
authored
Fixing typos in Allocation controller & related CRD message (#117)
1 parent 2e48100 commit 4028593

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/implementation/customresources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -408,7 +408,7 @@ status:
408408
solverPhase:
409409
endTime: "2023-11-16T16:16:49Z"
410410
lastChangeTime: "2023-11-16T16:16:49Z"
411-
message: Solver has enstablished a peering
411+
message: New active peering, triggered by Solver
412412
phase: Solved
413413
```
414414

pkg/rear-manager/allocation_controller.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -248,7 +248,7 @@ func (r *AllocationReconciler) handleK8SliceProviderAllocation(ctx context.Conte
248248
fcutils.IsNetworkingEstablishedOrExternal(fc) &&
249249
fcutils.IsAuthenticated(fc) &&
250250
!fcutils.IsUnpeered(fc) {
251-
klog.Infof("ForeignCluster %s is ready, incoming peering enstablished", contract.Spec.PeeringTargetCredentials.ClusterID)
251+
klog.Infof("ForeignCluster %s is ready, incoming peering established", contract.Spec.PeeringTargetCredentials.ClusterID)
252252
allocation.SetStatus(nodecorev1alpha1.Active, "Incoming peering ready, Allocation is now Active")
253253
} else {
254254
klog.Infof("ForeignCluster %s is not ready yet", contract.Spec.PeeringTargetCredentials.ClusterID)

0 commit comments

Comments
 (0)