-
Notifications
You must be signed in to change notification settings - Fork 48
Issues: wso2/k8s-api-operator
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Operator projects using the removed APIs in k8s 1.22 requires changes.
Type/Improvement
#606
opened Sep 1, 2021 by
camilamacedo86
API Operator logs an error after sometime an API is deployed - Status:409 Conflict
2.0.0
#593
opened May 3, 2021 by
renuka-fernando
Able to template HPA metrics configurations for TargetEndpoint and API
#489
opened Nov 9, 2020 by
renuka-fernando
Possibility to enable tracing with operator configuration instead of direct mustache configuration
#486
opened Nov 2, 2020 by
McMlok
Service catalog for K8s services
Priority/Low
Type/New Feature
#483
opened Oct 27, 2020 by
pubudu538
Ability to change the namespace wso2-system to some other namespace
#443
opened Aug 25, 2020 by
pubudu538
Dry-run is deprecated and can be replaced with --dry-run=client.. Error in latest kubectl
#425
opened Aug 8, 2020 by
pubudu538
Expose /authorize, /userinfo, /revoke and /token endpoints in Ingress level
#372
opened Jun 15, 2020 by
pubudu538
CHeck the possibility of moving from one API Operator version to another version
#369
opened Jun 11, 2020 by
pubudu538
Missing "omitempty" in json tag for non-required CRD Specs
#226
opened Mar 18, 2020 by
renuka-fernando
Add rediness and liveliness props to the deployment spec
#574
opened Oct 11, 2019 by
sajithaliyanage
ProTip!
Mix and match filters to narrow down what you’re looking for.