kind: feature
area: istioctl
issue:
  - 29026

releaseNotes:
- |
  **Added** `WorkloadEntry` resources will be read from all clusters in multi-cluster installations and do not need to be duplicated.
  Makes Virtual Machine auto-registration compatible with multi-primary multi-cluster. This feature is diabled by default and can be

	echo "BUG: PutObject to bucket: multi-key-poc without sse-kms should fail. Succedded"
	exit 1
fi

./mc cp /etc/hosts myminio1/multi-key-poc/hosts --enc-kms "myminio1/multi-key-poc/hosts=minio-default-key"
ret=$?
if [ $ret -ne 0 ]; then
	echo "BUG: PutObject to bucket: multi-key-poc with valid sse-kms should succeed. Failed"
	exit 1
fi

	// pattern ends in a multi. In that case, that multi is more general
	// than the remainder of the longer pattern, so combine those two relationships.
	if len(segs1) < len(segs2) && p1.lastSegment().multi {
		return combineRelationships(rel, moreGeneral)
	}
	if len(segs2) < len(segs1) && p2.lastSegment().multi {
		return combineRelationships(rel, moreSpecific)
	}
	return disjoint

        switch (subproject) {
            case "app":
                return newArrayList("multi/app/App", "multi/app/MessageUtils");
            case "list":
                return newArrayList("multi/list/LinkedList");
            case "utilities":
                return newArrayList("multi/utilities/JoinUtils", "multi/utilities/SplitUtils", "multi/utilities/StringUtils");
            default:
                return new ArrayList<>();
        }

For example:

[.multi-language-sample]
=====
[source, kotlin]
----
defaultTasks("some-task")      // Delegates to Project.defaultTasks()
reportsDir = file("reports")   // Delegates to Project.file() and the Java Plugin
----
=====
[.multi-language-sample]
=====
[source, groovy]
----

This is sometimes referred to as a multi-module project.
Gradle refers to modules as subprojects.

A multi-project build consists of one root project and one or more subprojects.

[[sec:project_structure]]
== Multi-Project structure

The following represents the structure of a multi-project build that contains two subprojects:

image::multi-project-structure.png[]

        }
    }

    def "instrumentation for #factory produces multi-release jar from multi-release original"() {
        given:
        def testFile = jar(testDir.file("thing.jar")) {
            manifest {
                mainAttributes.putValue("Multi-Release", "true")
            }

            entry("Foo.class", classOne())

It contains dependencies and other build information that is common to multiple subprojects:

[.multi-language-sample]
=====
.shared.gradle.kts
[source, kotlin]
----
repositories {
    mavenCentral()
}

dependencies {
    implementation("org.slf4j:slf4j-api:1.7.32")
}
----
=====
[.multi-language-sample]
=====
.shared.gradle
[source, groovy]
----
repositories {

  annotations:
    internal.istio.io/parents: HTTPRoute/multi-service.default
    internal.istio.io/route-semantics: gateway
  creationTimestamp: null
  name: multi-service-0-istio-autogenerated-k8s-gateway
  namespace: default
spec:
  gateways:
  - mesh
  hosts:
  - echo-1.default.svc.domain.suffix
  http:
  - match:
    - port: 80
    name: default.multi-service.0
    route:
    - destination:

A multi-project build is the standard in Gradle.

image::structuring-builds-1.png[]

A multi-project build consists of one root project and one or more subprojects.
Gradle can build the root project and any number of the subprojects in a single execution.

[[sub:project_locations]]
== Project locations