-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support egctl get describe different namespace #1197
support egctl get describe different namespace #1197
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #1197 +/- ##
==========================================
- Coverage 79.84% 79.72% -0.12%
==========================================
Files 152 152
Lines 17163 17196 +33
==========================================
+ Hits 13703 13709 +6
- Misses 2805 2828 +23
- Partials 655 659 +4 ☔ View full report in Codecov by Sentry. |
…ery status of non-traffic object
return res, nil | ||
} | ||
|
||
func defaultObjectNameSpace() string { | ||
return cluster.TrafficNamespace(cluster.NamespaceDefault) | ||
// trafficObjectStatusNamespace return namespace of traffic object status. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't understand this comment, what does it mean? And the following line also contains confusing grammar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for non-traffic objects, like autocertmanager, it is in namespace default, and its status is in namespace default.
but for traffic objects, they are managed by traffic controller, and traffic controller use specially prefix for status. for example, if a pipeline in namesapce default, then its status in namespace eg-traffic-default.
@@ -99,12 +97,6 @@ var _ easemonitor.Metricer = (*TrafficObjectStatus)(nil) | |||
|
|||
func init() { | |||
supervisor.Register(&TrafficController{}) | |||
api.RegisterObject(&api.APIResource{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why delete this registration?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cycle import, i move this registration to api pkg. it can't be solved by other way... i try it several times.
Co-authored-by: Yun Long <[email protected]>
Co-authored-by: Yun Long <[email protected]>
Co-authored-by: Yun Long <[email protected]>
Co-authored-by: Yun Long <[email protected]>
In Easegress, when using
IngressController
,MeshController
, orGatewayController
, resources such asHTTPServers
andPipelines
are created in separate namespaces to prevent conflicts. To access these resources, you can utilize the--namespace
or--all-namespaces
argument foregctl get
oregctl describe
command.This pr also fix some previous bugs about get status. In easegress, status and config of traffic object are put into different namespace.
For example, autocertmanager in default namespace, then its status is in default namespace too. But for httpserver (which is traffic object), if httpserver is in default namespace, then its status is in eg-traffic-default. When store status, traffic controller use a special prefix for it.