Skip to content

Commit 221c4d3

Browse files
Fix link for component architecture image
Signed-off-by: Madhav Jivrajani <[email protected]>
1 parent 3317d4c commit 221c4d3

File tree

1 file changed

+1
-1
lines changed
  • keps/sig-cluster-lifecycle/wgs/783-component-base

1 file changed

+1
-1
lines changed

keps/sig-cluster-lifecycle/wgs/783-component-base/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ flag names follow a consistent pattern? Are configuration sources consistently m
6161
and the config file correctly? Is the logging mechanism set up in a testable manner? Can it be verified that the HTTP server has the standard endpoints registered and working? Can it be
6262
verified that authentication and authorization is set up correctly?).
6363

64-
![component architecture](component-arch.png)
64+
![component architecture](../component-arch.png)
6565

6666
This document proposes to create a new Kubernetes staging repository with minimal dependencies (_k8s.io/apimachinery_, _k8s.io/client-go_, and _k8s.io/api_) and good documentation on how
6767
to write a Kubernetes-aware component that follows best practices. The code and best practices in this repo would be used by all the core components as well. Unifying the core components

0 commit comments

Comments
 (0)