[CDAP-21096] Split Appfabric into stateless service and stateful processor #123
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Make appfabric service stateless by splitting it into appfabric service to server HTTP requests and appfabric processor to run subscriber services and process message.
Change Description
Upgrade from Golang 1.19 to 1.23 since:
controller-runtime/tools/setup-envtest@latest
is compatible with golang version 1.19.go.sum
was generated by runninggo mod tidy
.CDAP master types:
AppFabricProcessor
of typeAppFabricProcessorSpec
.AppFabricProcessorSpec
consists of stateful specCDAPStatefulServiceSpec
.AppFabricSpec
to stateless specCDAPScalableServiceSpec
.deployment.go:
Auto-generated files:
api/v1alpha1/zz_generated.deepcopy.go
config/crd/bases/cdap.cdap.io_cdapmasters.yaml
Verification
make test
.cdap-operator
image to a k8s cluster and verified by deployed CRD and CR.