|
| 1 | +v2.2.8 Release Notes - August 8, 2022 |
| 2 | +===================================== |
| 3 | + |
| 4 | +Improvements |
| 5 | +------------ |
| 6 | + |
| 7 | +**peer - Ability to override core.yaml chaincode.externalBuilders via environment variable** |
| 8 | + |
| 9 | +Since chaincode.externalBuilders is an array, it previously was not possible to set via environment variable override. |
| 10 | +It is now possible to override chaincode.externalBuilders using an environment variable |
| 11 | +using the format CORE_CHAINCODE_EXTERNALBUILDERS=[{name: x, path: dir1}, {name: y, path: dir2}]. |
| 12 | + |
| 13 | + |
| 14 | +Dependencies |
| 15 | +------------ |
| 16 | +Fabric v2.2.8 has been tested with the following dependencies: |
| 17 | +* Go 1.18.2 |
| 18 | +* CouchDB v3.2.2 |
| 19 | + |
| 20 | +Fabric docker images on dockerhub utilize Alpine 3.16. |
| 21 | + |
| 22 | +Deprecations (existing) |
| 23 | +----------------------- |
| 24 | + |
| 25 | +**FAB-15754: The 'Solo' consensus type is deprecated.** |
| 26 | + |
| 27 | +The 'Solo' consensus type has always been marked non-production and should be in |
| 28 | +use only in test environments, however for compatibility it is still available, |
| 29 | +but may be removed entirely in a future release. |
| 30 | + |
| 31 | +**FAB-16408: The 'Kafka' consensus type is deprecated.** |
| 32 | + |
| 33 | +The 'Raft' consensus type was introduced in v1.4.1 and has become the preferred |
| 34 | +production consensus type. There is a documented and tested migration path from |
| 35 | +Kafka to Raft, and existing users should migrate to the newer Raft consensus type. |
| 36 | +For compatibility with existing deployments, Kafka is still supported, |
| 37 | +but may be removed entirely in a future release. |
| 38 | +Additionally, the fabric-kafka and fabric-zookeeper docker images are no longer updated, maintained, or published. |
| 39 | + |
| 40 | +**Fabric CouchDB image is deprecated** |
| 41 | + |
| 42 | +v2.2.0 added support for CouchDB 3.1.0 as the recommended and tested version of CouchDB. |
| 43 | +If prior versions are utilized, a Warning will appear in peer log. |
| 44 | +Note that CouchDB 3.1.0 requires that an admin username and password be set, |
| 45 | +while this was optional in CouchDB v2.x. See the |
| 46 | +[Fabric CouchDB documentation](https://hyperledger-fabric.readthedocs.io/en/v2.2.0/couchdb_as_state_database.html#couchdb-configuration) |
| 47 | +for configuration details. |
| 48 | +Also note that CouchDB 3.1.0 default max_document_size is reduced to 8MB. Set a higher value if needed in your environment. |
| 49 | +Finally, the fabric-couchdb docker image will not be updated to v3.1.0 and will no longer be updated, maintained, or published. |
| 50 | +Users can utilize the official CouchDB docker image maintained by the Apache CouchDB project instead. |
| 51 | + |
| 52 | +**FAB-7559: Support for specifying orderer endpoints at the global level in channel configuration is deprecated.** |
| 53 | + |
| 54 | +Utilize the new 'OrdererEndpoints' stanza within the channel configuration of an organization instead. |
| 55 | +Configuring orderer endpoints at the organization level accommodates |
| 56 | +scenarios where orderers are run by different organizations. Using |
| 57 | +this configuration ensures that only the TLS CA certificates of that organization |
| 58 | +are used for orderer communications, in contrast to the global channel level endpoints which |
| 59 | +would cause an aggregation of all orderer TLS CA certificates across |
| 60 | +all orderer organizations to be used for orderer communications. |
| 61 | + |
| 62 | +**FAB-17428: Support for configtxgen flag `--outputAnchorPeersUpdate` is deprecated.** |
| 63 | + |
| 64 | +The `--outputAnchorPeersUpdate` mechanism for updating anchor peers has always had |
| 65 | +limitations (for instance, it only works the first time anchor peers are updated). |
| 66 | +Instead, anchor peer updates should be performed through the normal config update flow. |
| 67 | + |
| 68 | +**FAB-15406: The fabric-tools docker image is deprecated** |
| 69 | + |
| 70 | +The fabric-tools docker image will not be published in future Fabric releases. |
| 71 | +Instead of using the fabric-tools docker image, users should utilize the |
| 72 | +published Fabric binaries. The Fabric binaries can be used to make client calls |
| 73 | +to Fabric runtime components, regardless of where the Fabric components are running. |
| 74 | + |
| 75 | +**FAB-15317: Block dissemination via gossip is deprecated** |
| 76 | + |
| 77 | +Block dissemination via gossip is deprecated and may be removed in a future release. |
| 78 | +Fabric peers can be configured to receive blocks directly from an ordering service |
| 79 | +node by using the following configuration: |
| 80 | +``` |
| 81 | +peer.gossip.orgLeader: true |
| 82 | +peer.gossip.useLeaderElection: false |
| 83 | +peer.gossip.state.enabled: false |
| 84 | +peer.deliveryclient.blockGossipEnabled: false |
| 85 | +``` |
| 86 | + |
| 87 | +**FAB-15061: Legacy chaincode lifecycle is deprecated** |
| 88 | + |
| 89 | +The legacy chaincode lifecycle from v1.x is deprecated and will be removed |
| 90 | +in a future release. To prepare for the eventual removal, utilize the v2.x |
| 91 | +chaincode lifecycle instead, by enabling V2_0 application capability on all |
| 92 | +channels, and redeploying all chaincodes using the v2.x lifecycle. The new |
| 93 | +chaincode lifecycle provides a more flexible and robust governance model |
| 94 | +for chaincodes. For more details see the |
| 95 | +[documentation for enabling the new lifecycle](https://hyperledger-fabric.readthedocs.io/en/release-2.2/enable_cc_lifecycle.html). |
0 commit comments